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 129e48b732fc 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 8496fe3bc1a7 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 503e35f40b01 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 38be421951a0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 897670a50ac2 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards e7a92078c4d8 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 4b99e8f1b814 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 03b4ecf589a2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 8504d30b8844 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards d6d95d2b3bf2 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 75370d801ab1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 568e188496a4 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards d055b6f1d478 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 396ae99add23 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards f6ffd704c029 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards f7571785f83f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 8e35e3fe175b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 9baa7eada5f4 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards b925faa25ad8 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards d23665fb5f4c 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 0156b37d9663 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards eebd14c58b19 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards d6b85de78e64 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 087f502a48ef 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 9581f50a3276 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 6f59e171eea5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards faf74236d7dd 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards fdf3664397a2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards f50cce888e21 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 5d31982f37de 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 6b2b16b05ddc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards b8e7ef16d08a 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 1b9e63b20231 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 62c20ce37e3b 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards cb880b4d1e18 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 026c3c9f0570 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 90319bfb5b94 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 01f9a7e36b52 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 309c6e483d24 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 925e12444f63 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 9593bc3d8918 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0f5cb12627ef 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards f9f12c77ed4e 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 1c70979aa652 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 4a78e7e96659 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards d8e2a3f46add 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 01c0505eb294 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 1045654762d1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 70b6dec08d90 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 9a2d1384724d 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards a88c0c68f794 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 4941f7e0a172 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards cd6f691c6cae 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 29485ac7e648 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 1f344202b9d1 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 9b2755c2f32e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards b21d9efc77b9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 9dbf2053f905 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b3c02b8b54f2 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 4a691cea0296 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 5215990d1052 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 905782c85012 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 34b0c3980622 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards c922db00258a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards c17ab2c37d46 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards df3edba4365a 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards fd44afc83688 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards c55baca1aea1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards ab0ebf298ea1 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards f88e4f6a5c6f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 99ecf0c01a78 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards d9c20b0d8584 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 185bf47adb08 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards a702bdaecae0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 32087d4531f5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 19710419d3be 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 2be30fe83b68 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards af380bd4c3c7 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards ea53c5692d62 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 6f9929b35c59 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 0ff95510fa8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 4e66faacb818 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 3b32280af239 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 03a4acc8a836 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards c9d51f37f6e9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 5bc639670fff 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 527ff5e6f308 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards bf75c0b4300d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards b6d569cf1516 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 672143ba3476 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 86e47d6f64fb 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 6f29de6ec50e 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 5206b8321db4 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards a414a30f2a5d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards a53689798f2f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 7a6ac19f2339 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 91e88e6f6aab 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards d70aad100480 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards f96119795824 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards a45f0d7013f4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] discards 478fbec4653c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] new 1b47a837f973 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] new 1876211bed14 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new adf6561ca92b 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 99ac52e8f172 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 4c447dddff49 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 73fea962bd36 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 885c3b3448f3 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new 18c9b043161d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 582778c4ff7d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new a7ed9a61b638 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 52584aad57ee 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 704e05d3f839 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new dd5e0f240d0d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new e33c89f54d3f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 44aeffb47036 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 859921c99eb8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 98626fb68c92 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 5119ff0e004a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 2a3d863f12eb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new abae20cd89a0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new decf4d049479 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 0cb8ee45d8c1 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new d75a7df17d9a 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 3c6572b82358 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 3546426d4a7a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new fffd73fced57 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 034bd10a2231 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 715836774602 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 0d430d9f564c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 44c70c688d7e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 684089eccf38 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new beb812d5afc7 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new be29aba3f629 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 78f7717c4265 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 3f7ad481f49e 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 31cf82168abd 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 83b9850e6220 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new b0c3a0c699eb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new c44ef668a45b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new a6fcd4da26ad 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 3f3867834569 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 67913b210da9 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 71301cd2ed51 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 84012412be6f 194: onsuccess: #1995: 1: Success after linux: 517 commits new a8e45411d150 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new d6868e7f3c93 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new aab7bd521201 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 9d2a8e36b560 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new ce421ad064b3 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 5abdb3af6d2b 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new bf0ab222ed5d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new de503396a72f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 8c41bae8e439 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 1388bdca6c14 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new aa9d5cca3912 205: onsuccess: #2006: 1: Success after gcc: 3 commits new dec28a40197a 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 5b99b2b715af 207: onsuccess: #2010: 1: Success after gcc: 4 commits new c1d81de49ed6 208: onsuccess: #2012: 1: Success after linux: 12 commits new 4aa4992b6d83 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 1a8906ff453b 210: onsuccess: #2017: 1: Success after binutils: 6 commits new dc0aef085c0d 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7e0d2a8608ca 212: onsuccess: #2022: 1: Success after linux: 3 commits new 37b62891a7e8 213: onsuccess: #2024: 1: Success after binutils: 3 commits new bab0dfe0f1bf 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 5f3eb0304257 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 0a19db511eba 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 1a2bf7be04c9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 6ecefdd5123c 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7928fb134708 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 95bd9a524aad 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 16eee2d5703a 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new e8fd22884bcd 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new f957991ef869 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 15f2a8915d7f 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 1bbb5609ac0b 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 9299e28e3500 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new eff05c96a5ab 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new e666c235b757 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 44883dd9d1f9 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new e8dce1b77162 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 6524a25c318b 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 8801a8d4facc 232: onsuccess: #2048: 1: Success after glibc: 2 commits new a8e5eb9d5164 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 5e38ad174635 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new d9e9f77d378f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new f10e5e8bef7c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new cfdc85ad54a9 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new aadb0ae80b1e 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new d90a6788ddd9 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 37050c199b4f 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new b489863d65e9 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 311abb663b41 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 683d914bc1be 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 6e3075945124 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new bf6832f02f9d 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 29e746669f19 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new e52b57644e10 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new b8f6a463f078 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new f8838cfeabfc 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new fcad6616defd 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 26c4989b2e04 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new f840a528fa32 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 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 (129e48b732fc) \ 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 1808 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32068 -> 33040 bytes 04-build_abe-stage1/console.log.xz | Bin 92232 -> 92368 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 235744 -> 237064 bytes 08-build_abe-stage2/console.log.xz | Bin 225704 -> 226844 bytes 09-build_abe-gdb/console.log.xz | Bin 39268 -> 39636 bytes 10-build_abe-qemu/console.log.xz | Bin 31316 -> 32012 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2760 -> 2776 bytes 13-check_regression/console.log.xz | Bin 6040 -> 5572 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 10 +- 13-check_regression/results.compare2 | 35 +- 13-check_regression/results.regressions | 27 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 27 - sumfiles/g++.log.xz | Bin 2657400 -> 2693360 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2276332 -> 2253092 bytes sumfiles/gcc.sum | 2572 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 901568 -> 903352 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214092 -> 214072 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435628 -> 439660 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 1413 insertions(+), 1470 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