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 f7033e5e9239 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards d40da9a3a212 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 4c08fa794bd1 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards ac7b5d517da9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 070d6a4bab21 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards b4f4e558d582 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 42f7d1c56b9e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 675e2cb5d351 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 3e0a3f071736 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 68aab529e61c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 0bf749ff234b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 3bba4a02b633 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 45780b31913f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards fe481a147ff7 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 5bb4a92b391c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards bead4acfaf44 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 09ff80d9c62a 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 8d5e4ccda9de 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards cb8174a674a8 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards e47b32f61d6b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 4c66599f046f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards a1cc19d6d2e6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 1c4934721078 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 372b2bd6500c 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards e730819cd47f 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 1328fe82ef4c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 6f6ece3a39c1 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 9292f7471281 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards bfd8bd5bafe4 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 71066a57083f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 38deaad878f7 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards f8e5f83734c1 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 1cbe038e2444 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 91729603b1c7 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards c3548de42589 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 741c10442db5 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 178ef0f715b8 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 39ffc521d828 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 58f281f9caa0 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 0bb4be89a83d 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 5a1c9e164012 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 14760e879e93 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards b45beddf7b69 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 84e9e4bbbf72 212: onsuccess: #2022: 1: Success after linux: 3 commits discards a8099fc04a91 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards e29706e5cf88 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 17b8b148eede 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards aafa2ef3420e 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 2a3b3f783812 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards ab17fe5e6b52 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 9000bd9cba30 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 819a585cfbfc 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 768c35b38c4d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards b3b567d9b2e1 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards cd7fe9f042de 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 528836545d51 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards c9b9b43c8ad8 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 07db7bd26725 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 130e0a8d97a5 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 90bcc58d4b1d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 751f6db1570e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards bf029dd02d6c 194: onsuccess: #1995: 1: Success after linux: 517 commits discards f8126c177823 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards af39bcf7b2d8 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards fb0794d97834 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 28de57a7e7cc 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards a9a3ebb1bc02 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 2c67ac0c3ed8 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards b4f4b885d448 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards be2a80386d25 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards f05d8f601649 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 0596d2aaa515 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 90985cb032dd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards d3af6d9d736e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 28161794777a 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 2477940e67e5 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards d679ba6c9ac9 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 5eff1709fdfe 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards c78619c57b8a 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 4396c982c3dd 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 8820d5ce21fb 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 5e6c04c5bbff 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 575bfb514d59 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 0e90695b3af7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards efef3a8b93ea 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards c7c583895ee0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards d7d3e2509332 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 01b4910422d0 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards fb9b0fe870c3 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 075d643c09f4 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 949518218a48 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 00c9181bffdb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 17205032a3cc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 4c240fd123f9 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards f990947cb909 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards df71bdda597c 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 4930241c2213 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 429e293454e9 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 33c87cc47fcd 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 2686f80dc11e 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards d8c817a6333f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new f68384024b31 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 8c1706411d0c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new d605c4bb833c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new c4c2250cb2c1 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 376fa2c30e4b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 38a8bea3d34d 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 2246a6e365b7 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 4dc6410da06a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 5e59bb74c911 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new ae1e0f2f5dab 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 0dde33bc562b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 8fd061bd9a49 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 1db5a24434df 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new dc295698f360 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 6a11f461beef 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new ec1945a2949a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new e64e0dda6b89 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 05d095395a84 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 6ed74cc7090d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 97613457c19c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 09202dfeea9a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new f945e3edcac8 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 3f1cee537359 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 98019147be2f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 6d140475c2a2 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new ac5dbcf4497d 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 662750da193d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 7f76e1991f2e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 44ad0407b069 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new fb496e8d74fa 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 6fb76bb7fb80 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 57be0547678c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 439ce1dac541 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 3786ed2f3053 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 269d0ad59038 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 2156015e4761 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new a743b177baa4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new dc818809ebec 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 3a19d83de7ae 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 8cc9b627c93b 194: onsuccess: #1995: 1: Success after linux: 517 commits new 737209df0e43 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new fdbb3fb2a48b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new cd7e6546b669 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new ee862526c4b8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 30525e625406 199: onsuccess: #2000: 1: Success after gcc: 5 commits new d89e328fb175 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new be9e81384637 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 5bafa1aff269 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 3af9d07a651f 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new b944a2cc5476 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 1011a8d658d4 205: onsuccess: #2006: 1: Success after gcc: 3 commits new d9ffe00529d4 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 77cfd7cdc3bd 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 527799ed66af 208: onsuccess: #2012: 1: Success after linux: 12 commits new f844ba0d6c02 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0eee46398cfe 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 17388a72eaf9 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 1c2b6f0a3495 212: onsuccess: #2022: 1: Success after linux: 3 commits new 14f0ee7b8ed3 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 953902c80fa5 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new a417e14d6fa9 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 0f9fd2df3707 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 125280da929c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new d7fe60d2cd52 218: onsuccess: #2030: 1: Success after gcc: 5 commits new a198446826a2 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 0a197e185a9d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 17c15fb9a518 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new c1b193c168bf 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 6e4961b9eb50 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 18f9b07b719b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 1111a46a4d42 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 337de9d8fe33 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 2af2da0bf852 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new d091561ee179 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 35d92d5bf4f2 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 15a0b82ba35c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 467b982eda89 231: onsuccess: #2047: 1: Success after gcc: 4 commits new cda84798c7a7 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 1d3b52cdbe61 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new b14874ce852f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 959b31e0879f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 02c0c0021f09 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new bbbe44b457f2 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 0f7048b07e2c 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new b0b85e82b5c3 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new cab6874fccbe 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new bd9428bd4510 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 5fb544239fda 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 8af16402f289 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new a7f956ca6a08 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 1cb2fd8a751f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new f6586c9680a5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 2aa05335921a 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 9f13bb0d730d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 5263ab6efa5a 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 8b3289b777a8 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 90ca802ece24 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 7dcead1cae30 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 335809a7ea72 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new f10a1a8d1a30 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new b5053432bd1d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 09b3dd4fa4af 256: onsuccess: #2072: 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 (f7033e5e9239) \ 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 1792 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31848 -> 32300 bytes 04-build_abe-stage1/console.log.xz | Bin 91348 -> 91624 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 234980 -> 235776 bytes 08-build_abe-stage2/console.log.xz | Bin 223856 -> 224348 bytes 09-build_abe-gdb/console.log.xz | Bin 38956 -> 39300 bytes 10-build_abe-qemu/console.log.xz | Bin 30944 -> 31564 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2668 bytes 13-check_regression/console.log.xz | Bin 5592 -> 5788 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 | 40 +- 13-check_regression/results.compare2 | 30 +- 13-check_regression/results.regressions | 27 - 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 42 +- manifest.sh | 34 +- results | 27 - sumfiles/g++.log.xz | Bin 2684072 -> 2661036 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2244992 -> 2273452 bytes sumfiles/gcc.sum | 2498 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895012 -> 900152 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214008 -> 213872 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428496 -> 441540 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 1489 insertions(+), 1539 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