This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards b4137c326c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards ee51ebcd66 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 222465a5ad 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards f6b4e1e36b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 85561786a6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 7bf6147eb2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 5c3fe2235c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards c231750a19 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 4411912446 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards f7b3ba45df 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 3fdd23b606 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards db092e2cf7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 5c07e711ee 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 91b4b4cc98 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 04ca72da2c 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 9f95b6087d 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards cd17256433 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 78d8cfd187 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards e8a64da153 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 76e095d108 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 0137a89778 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 73ad0ff75d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards a01f85cdb1 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 36c82fb5d1 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 99541155e9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 4070817de6 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards a781d8650b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 7fb81fe1a3 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards a0567f40ce 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 43e3105a69 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 5f77029b95 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards e52a2c7884 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards eee4aa65e5 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 3d65902793 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 2078e9211d 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 79e0d88a57 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 20a9b29712 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 723501952a 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 6a4d2525b6 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards b00b7abb5d 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 27a0a53621 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards b68788792d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 1fafeeeeee 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 6f9200c98f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 52d6bac7ef 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 2e4946c0a1 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards d6192107db 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 86ec6e1bbf 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 6ae67afe89 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 60d6918c05 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards b72dab2471 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 9f7454cf10 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 86e1327b29 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 9e9131230b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 90855f3e28 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 59ad0c3f2e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 3951d2ac48 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 9738a23e14 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 104072b49b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 3583acd053 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 285d271eef 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards c2609353fd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 372a1cbbc1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 193685dc9a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards edadea3b9e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 41a55fa77a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 84998a1b08 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards c1836cd156 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards e0250b14fc 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 2cf1acb1f4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 83c800c0df 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 7da61e5106 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards dc0f5adfdf 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 734729d142 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards f3d5c3deb3 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 9b62bc9312 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 20577d286e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 834f14b43e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards e38700f069 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 8e6953c4c5 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards eb7bf6a38e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 32480913aa 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 60eab3e388 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards e207591d27 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards bc49e6a2db 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 5f007222ef 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 552baa5526 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 43639b80c4 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards a63284837a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 997d2737e1 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 206f841a70 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards b816d2a42b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards a73bc8d300 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 8edabf2364 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f690099c8f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards b310221c48 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cae44eb8d5 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards e4ca8d5e56 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 158114600b 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 2ccd815974 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 94d72315be 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new ef953d2134 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 1fcf56ae5c 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new c74f76c8e9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c47da0be23 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new f093bc63e3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 39b7c87096 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3ff95a7c9d 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 3f362c8f94 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new e9150c8219 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 6104bc01f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 16df8c4426 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 2751df6290 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 9665865991 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6ae32a9fe0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1d28463952 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new c123dd5e76 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f66923fcdd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 03e070b33a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 3c5ee38e1b 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 6af13186a6 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 0492cc507b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 71cbdf37b4 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 17299f5eef 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 8ebe0e5772 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 73cd3bda9a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new de1e18b741 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new be4a0f5c29 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 7f20bf1e06 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d511aa0049 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new fc103c868b 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 850dd8e5f5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 9658bbcbe8 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new c1b35adfa5 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new d4bf1b4e5e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new b521ea4122 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 808d2d291b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 2c18a7181a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new b542e878d0 128: onsuccess: #1723: 1: Success after linux: 12 commits new f2cc8a71fe 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 113291a174 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 338394297d 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a300bbe3a5 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new ff5f1ca3fd 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 2b6612ad51 134: onsuccess: #1730: 1: Success after binutils: 2 commits new bc3871451f 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 925e31101f 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 34887e1cb1 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 6c9b4a7d2b 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new db89e87c55 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new c7914ed7ec 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new ab277053a0 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new d6fcfc6b91 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 08edb8b223 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new b3b29b7f3a 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 9f6b1985eb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 8c0c6312f4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new bfdad10811 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new d461541f92 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new eb407b58b9 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 9fe7d9097d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 66cabc2bed 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new bd245bb205 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new abfdf23126 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 7d1742b1e7 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new b9a912ba28 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 7b482acd80 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 969cbacd24 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new d879f0c554 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new e0b23c4a34 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 622cb52999 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 5b80f70c8a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new a7b949e168 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 5975b740c9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new d3dca8e1ca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 9e6af8831b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 5244e99528 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new 4571bdfcba 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new e61707b430 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new d1d194ea6d 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 10538c8095 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new c1f26b07a0 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 14d1f2b5dc 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new be1e9cec6b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 0e92ed9a3a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 0288441901 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new e1a3c80dc2 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 46e390853a 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new e526f74dde 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 0b6fc66319 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 751d5874c9 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 4ffd50466e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new adc07acf69 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 064e1d5b96 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new b9c40021b9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new c6b1d6aea8 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 721bab0878 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 0410f35879 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 58c673840c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new c1725ec08a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 39f05b2b97 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 164155607e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new a96bf5d3b0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (b4137c326c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1684 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31320 -> 31600 bytes 04-build_abe-stage1/console.log.xz | Bin 91248 -> 91532 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 234896 -> 235300 bytes 08-build_abe-stage2/console.log.xz | Bin 224852 -> 224728 bytes 09-build_abe-gdb/console.log.xz | Bin 38668 -> 39040 bytes 10-build_abe-qemu/console.log.xz | Bin 31032 -> 31324 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2612 -> 3148 bytes 13-check_regression/console.log.xz | Bin 16456 -> 5848 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 19 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 52 +- 13-check_regression/results.compare2 | 1863 +------------------- 13-check_regression/results.regressions | 53 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 53 - sumfiles/g++.log.xz | Bin 2733584 -> 2739956 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 2243772 -> 2230452 bytes sumfiles/gcc.sum | 2919 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 892252 -> 889972 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212884 -> 212812 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433372 -> 426608 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 1712 insertions(+), 3720 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions