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 d7ad7a397f72 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards bd090c8567ee 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 9ad4e6b78649 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 96525e2573fc 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards ac0fd2d76ac0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards f9fbbfef2dff 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards f979389bf2a6 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 9061afb3199f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 1285b4f91031 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 2b2994eef8ad 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 1784b127d780 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 1c52ec65ad2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards f35b8fef6a0b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 2a2873bed511 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 50c30b59653f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards f27ca2705c9a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards c073e309f48f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 13d029a6fdbd 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards f1ceb4e05fab 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 139176510976 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 7299d54234e1 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 8ef40a95f95d 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 07923b19c020 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 95b0d8a89e76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 62bcb20bb243 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 47cf2a7a2778 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 60806d72efda 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 37283eacbc5f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards c47b23af178a 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 5f109e19fa21 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards f22a32930a4e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 5ae26f010f3a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 176fecbab806 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 9fb34c2941e3 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 6ae0e9f84665 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 1940cd420dcd 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards d4ff1ebd9c7c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards f839f0a4f425 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 5982686cf0cb 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c24888e6d148 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 49bf27a30e23 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards fe60b74d1fe4 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 6000f3e7ed5e 208: onsuccess: #2012: 1: Success after linux: 12 commits discards c16043f3c111 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards d6cc7ef82e92 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards b2fc45b788eb 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 905f772b17dd 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 4e168576d641 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 32e4e6d98f09 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards a2f2153e45d5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 1421cb78fbe9 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 54d945e69dfb 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards a55617534d66 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 43a3d05cb86e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 035c9dfd6c20 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 800fcf8a7ccc 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 9218f0891f32 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 1e1ce9c91ed4 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards e4fd8ed5810f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 52de999f5a6c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 1671d359729b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 7635b66d604a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards bc8825da9999 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 65f690c25898 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 8518edb64b85 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 45dcdbb2bf3f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 858e0e726fb3 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 08b01b9d1faf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards cffbb5020a80 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 5dbb4b050e1f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 85712818fddf 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 5ed8d7fb4dd8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards d5dcc1780a8e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 6df9c490e484 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 760262dd7481 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 3a69ba2fda06 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards d04a5cdde038 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 45e8537e6603 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 1e6703ff6cf1 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards c625c5654548 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards c0fa322e178e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards ceb45f47bccb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 9014b4fd750c 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 8c749d625702 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards a758d5a4d3ee 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards bc22f8857cc2 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 1f81a1a66d8a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 67fb83e3dcf7 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ba9c0c3d82ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 1e14881db9d2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards c4b40b5e0094 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 1718dc72d6a7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 2ad389cdaa20 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 24d5125e01c5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards bcd9a15ad28b 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards c670ebb8a605 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards c0ec92fdf39e 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 7b2d9e4e5e58 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 18686176b12c 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] discards 0af33cc6a538 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] discards e37931a516f3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] new 9a35d2b9963c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] new 478fbec4653c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] new a45f0d7013f4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new f96119795824 153: onsuccess: #1754: 1: Success after gcc: 2 commits new d70aad100480 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 91e88e6f6aab 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 7a6ac19f2339 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a53689798f2f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new a414a30f2a5d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 5206b8321db4 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 6f29de6ec50e 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 86e47d6f64fb 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 672143ba3476 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new b6d569cf1516 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new bf75c0b4300d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 527ff5e6f308 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 5bc639670fff 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new c9d51f37f6e9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 03a4acc8a836 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 3b32280af239 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 4e66faacb818 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 0ff95510fa8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 6f9929b35c59 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new ea53c5692d62 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new af380bd4c3c7 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 2be30fe83b68 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 19710419d3be 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 32087d4531f5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new a702bdaecae0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 185bf47adb08 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new d9c20b0d8584 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 99ecf0c01a78 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new f88e4f6a5c6f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new ab0ebf298ea1 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new c55baca1aea1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new fd44afc83688 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new df3edba4365a 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new c17ab2c37d46 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new c922db00258a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 34b0c3980622 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 905782c85012 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 5215990d1052 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 4a691cea0296 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new b3c02b8b54f2 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 9dbf2053f905 194: onsuccess: #1995: 1: Success after linux: 517 commits new b21d9efc77b9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 9b2755c2f32e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 1f344202b9d1 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 29485ac7e648 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new cd6f691c6cae 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 4941f7e0a172 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new a88c0c68f794 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9a2d1384724d 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 70b6dec08d90 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 1045654762d1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 01c0505eb294 205: onsuccess: #2006: 1: Success after gcc: 3 commits new d8e2a3f46add 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 4a78e7e96659 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 1c70979aa652 208: onsuccess: #2012: 1: Success after linux: 12 commits new f9f12c77ed4e 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0f5cb12627ef 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 9593bc3d8918 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 925e12444f63 212: onsuccess: #2022: 1: Success after linux: 3 commits new 309c6e483d24 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 01f9a7e36b52 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 90319bfb5b94 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 026c3c9f0570 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new cb880b4d1e18 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 62c20ce37e3b 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 1b9e63b20231 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new b8e7ef16d08a 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 6b2b16b05ddc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 5d31982f37de 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new f50cce888e21 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new fdf3664397a2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new faf74236d7dd 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 6f59e171eea5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 9581f50a3276 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 087f502a48ef 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new d6b85de78e64 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new eebd14c58b19 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 0156b37d9663 231: onsuccess: #2047: 1: Success after gcc: 4 commits new d23665fb5f4c 232: onsuccess: #2048: 1: Success after glibc: 2 commits new b925faa25ad8 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 9baa7eada5f4 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 8e35e3fe175b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new f7571785f83f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new f6ffd704c029 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 396ae99add23 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new d055b6f1d478 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 568e188496a4 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 75370d801ab1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new d6d95d2b3bf2 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 8504d30b8844 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 03b4ecf589a2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 4b99e8f1b814 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new e7a92078c4d8 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 897670a50ac2 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 38be421951a0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 503e35f40b01 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 8496fe3bc1a7 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 129e48b732fc 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...]
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 (d7ad7a397f72) \ 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 1776 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31832 -> 32068 bytes 04-build_abe-stage1/console.log.xz | Bin 92060 -> 92232 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 236008 -> 235744 bytes 08-build_abe-stage2/console.log.xz | Bin 223876 -> 225704 bytes 09-build_abe-gdb/console.log.xz | Bin 39064 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31544 -> 31316 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2528 -> 2760 bytes 13-check_regression/console.log.xz | Bin 6976 -> 6040 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 57 +- 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 27 + 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 | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 2676612 -> 2657400 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2246304 -> 2276332 bytes sumfiles/gcc.sum | 2546 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 898060 -> 901568 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214104 -> 214092 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436908 -> 435628 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 1494 insertions(+), 1458 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions