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 09b3dd4fa4af 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards b5053432bd1d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards f10a1a8d1a30 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 335809a7ea72 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 7dcead1cae30 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 90ca802ece24 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 8b3289b777a8 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 5263ab6efa5a 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 9f13bb0d730d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 2aa05335921a 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards f6586c9680a5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 1cb2fd8a751f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards a7f956ca6a08 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 8af16402f289 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 5fb544239fda 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards bd9428bd4510 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards cab6874fccbe 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards b0b85e82b5c3 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 0f7048b07e2c 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards bbbe44b457f2 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 02c0c0021f09 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 959b31e0879f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards b14874ce852f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 1d3b52cdbe61 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards cda84798c7a7 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 467b982eda89 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 15a0b82ba35c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 35d92d5bf4f2 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards d091561ee179 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 2af2da0bf852 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 337de9d8fe33 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 1111a46a4d42 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 18f9b07b719b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 6e4961b9eb50 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards c1b193c168bf 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 17c15fb9a518 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 0a197e185a9d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards a198446826a2 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards d7fe60d2cd52 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 125280da929c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 0f9fd2df3707 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards a417e14d6fa9 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 953902c80fa5 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 14f0ee7b8ed3 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 1c2b6f0a3495 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 17388a72eaf9 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0eee46398cfe 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards f844ba0d6c02 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 527799ed66af 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 77cfd7cdc3bd 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards d9ffe00529d4 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 1011a8d658d4 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b944a2cc5476 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 3af9d07a651f 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 5bafa1aff269 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards be9e81384637 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards d89e328fb175 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 30525e625406 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards ee862526c4b8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards cd7e6546b669 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards fdbb3fb2a48b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 737209df0e43 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 8cc9b627c93b 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 3a19d83de7ae 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dc818809ebec 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards a743b177baa4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 2156015e4761 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 269d0ad59038 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 3786ed2f3053 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 439ce1dac541 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 57be0547678c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 6fb76bb7fb80 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards fb496e8d74fa 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 44ad0407b069 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 7f76e1991f2e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 662750da193d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards ac5dbcf4497d 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 6d140475c2a2 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 98019147be2f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 3f1cee537359 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards f945e3edcac8 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 09202dfeea9a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 97613457c19c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 6ed74cc7090d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 05d095395a84 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards e64e0dda6b89 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards ec1945a2949a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 6a11f461beef 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards dc295698f360 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 1db5a24434df 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 8fd061bd9a49 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 0dde33bc562b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards ae1e0f2f5dab 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 5e59bb74c911 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 4dc6410da06a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 2246a6e365b7 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 38a8bea3d34d 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 376fa2c30e4b 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards c4c2250cb2c1 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards d605c4bb833c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 8c1706411d0c 156: onsuccess: #1757: 1: Success after gcc: 4 commits new db954b02e238 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f1852819c17e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new ff4a99060321 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 173cc5e09faa 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 1e6b6a6c6676 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 834b5853dbe2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 6b216478f7e4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 0d6641a9f9a8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 53f2e698ce4f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 8c71116e27b3 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 306d97ced349 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new ce9e154f5a9c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 7c0b6bfddf4a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 7ab17d0cfb4b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new a7735144414b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new c40b1358412d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 0287f253700b 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 00682e9ec538 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 6c2b9f94c3b3 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 474fa27bceca 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new ca90cebbdc67 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new d216f06496f5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 1141bd9e43bc 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 3a8d752c9b85 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new b505af354fb5 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 7e114c080ee1 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 98b9118af96f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new c02e30fe3897 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 24db4e491445 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 8460ddbc4c55 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new d449c700a249 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new da4dfae34b6b 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 570dca2d0e69 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 9f48f1f94bfa 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new b9e3541547a4 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 827b23fe00c2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new ce71224c7b60 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 3b2d86660ccc 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 017d95140327 194: onsuccess: #1995: 1: Success after linux: 517 commits new 895d4812ae0e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 70cf7a3300fa 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new e04a629d2638 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 57ed7510e521 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new f7c82d636bac 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 65ada14592ad 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new be211975c160 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b3709dc2290c 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new fd0418e80a66 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new bc1837cb4d12 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 308f3d6fd77a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new c5d96173557a 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 318a5b81b18c 207: onsuccess: #2010: 1: Success after gcc: 4 commits new bea4ef7a1f42 208: onsuccess: #2012: 1: Success after linux: 12 commits new 434df638aed3 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 5a157b06a66a 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 57fb2e33e607 211: onsuccess: #2020: 1: Success after binutils: 10 commits new dff6b29ece1a 212: onsuccess: #2022: 1: Success after linux: 3 commits new 927258c3c3ea 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 950170986868 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 0f33bfd8de3e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new a328a6105e0f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 28b8daa71f6b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 87659d75df98 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 157003af12af 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 30b0c7c4fe2c 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new b20ca53d43e9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 92b49b78a3f6 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new f509156763be 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 47d361c2d210 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new b9fa2b6dfd73 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 71573171ec0c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new d729fbddcc36 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 2bd12974a0a5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new bc5dd2b1d976 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new e7c3a0fabb23 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new ee376e3ac805 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 35eb97a0525d 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 25baf15d7215 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 480c74b5eeb6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 43e2458483eb 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new b307045943bc 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 71618b70c389 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 04658dfe4969 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 922ede864f5c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new bc142d5c53d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new de154c5b9481 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new b0e63045a5e4 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 72ecc038539e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new d306d2f125c2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new ed0966388b2a 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 76ed5eec9f81 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 54b3662dc97e 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 6da47e13570b 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 689a422805d2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new a26d37750d35 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 256f17b40d86 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 4c18bdc13d67 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new c7d97ebf65a3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 0caa70413259 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new a8ce467e433f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 1e803eb14591 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 9c52f087f6e8 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...]

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 (09b3dd4fa4af) \ 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 1796 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32300 -> 31756 bytes 04-build_abe-stage1/console.log.xz | Bin 91624 -> 91568 bytes 06-build_abe-linux/console.log.xz | Bin 8644 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 235776 -> 234532 bytes 08-build_abe-stage2/console.log.xz | Bin 224348 -> 225084 bytes 09-build_abe-gdb/console.log.xz | Bin 39300 -> 39104 bytes 10-build_abe-qemu/console.log.xz | Bin 31564 -> 30636 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 2656 bytes 13-check_regression/console.log.xz | Bin 5788 -> 5448 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 53 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 21 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 26 + sumfiles/g++.log.xz | Bin 2661036 -> 2652424 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2273452 -> 2271896 bytes sumfiles/gcc.sum | 2498 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 900152 -> 892564 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213872 -> 214016 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441540 -> 435400 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1450 insertions(+), 1407 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