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 243b1b55d2 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 427ab69a44 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 981215969a 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 8af1a01a24 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards ec9a0834d6 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards da9968ac20 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 0cd9ef8054 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 643ec2de2b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 85a263ba36 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 76d7174664 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 16b3fd00d8 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards fc98c39982 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ea83eb851f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 50d58cb04f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 22f8916dd7 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 04db8febcf 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 59b6f0278c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 30fca8e9e8 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 24301c141f 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards e70ca85d4b 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1a2d8fdb5d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards a5f9618d1f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 9c5e5fe4ce 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 8b3ffafedb 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 02e86d3fa2 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards c4814d3098 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 442ca97846 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 7cff4d45d4 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 4e8c7997ff 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 1791d9f768 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 4d0f5a9c45 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards b991ee420a 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards db59d34d2c 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 892dbe1795 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 283ed94eb3 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 0372d80dfe 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 2ca944e76c 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards e74e25bf70 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 7a749ad775 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 0208d93219 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 3c7f44932f 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 5f7c903750 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards fa0206f699 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 29dbeaa965 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 248463e71c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards e8ae9ddbed 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 6f7c94c1d0 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 4e797f90c9 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 75ccac3a8f 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 396ba9b20b 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards d8fb52eafa 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards ea6ed4d204 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards e7455fafaa 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 62f1207e6f 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 7276a8af69 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 2c4b28a1cc 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 3d02e528d2 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 78c8bf457f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 4896b649ed 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 123327233a 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 895bc1529f 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 69a1ec092b 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards e29fdeaf62 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards ceb48cd54f 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 3c180fd3df 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 6a2935b58b 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 362965dc07 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 06a6f98afe 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 9ac7c072c1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards d49a584204 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 0a6138f00b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 91856bc522 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 5368ee5620 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 372aae537e 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards ea6ae3509c 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 3b5a075c45 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 78e073b214 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 8d71f7511e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 4a860b7853 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 3c8cd5432f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards f09e3f4cc3 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 7150c74c99 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 8b26273970 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 18ce9d648d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 7465c06ecb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 4b2669510a 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards e12b9d9a5c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards ed718c1e2d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 467bd81d32 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 146a8dd7fe 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards dffaa715f2 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards d81154db4f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards cc4b9a27b6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 50fe4065d0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 3bad7a1cf5 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards a07b32730d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards ed12d14367 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards ce3d065537 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards fc11752843 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards f921f96de2 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 69bcf1ee2d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new dec52aa765 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 2f87ea4481 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new cc1a158998 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 94e79746ff 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 2494dbbf64 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new fc70a1add5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 01a613a06c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new e40270272c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 48b019c76c 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 08394a3c6f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 3af3b90b04 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new bea7233f61 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 31b6033f7f 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 2c5b0f1f9b 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new c6dbd40d14 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new d416c4bf64 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 0442b15452 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 921cf5dc1b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 0ae74526d1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new 34fc62946d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 25dab114df 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new f2ca286f0a 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 2be41f99b9 194: onsuccess: #1995: 1: Success after linux: 517 commits new f78f1c775b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new 2dad194079 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new fcb68324e4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 0f5d5f63ff 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new ee2e09897a 199: onsuccess: #2000: 1: Success after gcc: 5 commits new f33b3de315 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new aff89eb759 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 67383bce76 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 59e69cd965 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new eef089eff3 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 52094bca19 205: onsuccess: #2006: 1: Success after gcc: 3 commits new dcd32831e3 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 0e8c23eb2b 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 8f88a4c695 208: onsuccess: #2012: 1: Success after linux: 12 commits new c57c9a12ac 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 3a1ebba2ca 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 04de9af269 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 8d944e54d4 212: onsuccess: #2022: 1: Success after linux: 3 commits new da03236703 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 1fe3bbd63a 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new c9370a7002 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 190f779df8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 940579dc94 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 0823ddf5e8 218: onsuccess: #2030: 1: Success after gcc: 5 commits new b8c1cbc1e9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 1cfae1a74b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 7a581726d4 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new b19ae65989 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 68ef81b797 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 001f92f907 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new c8e51f6063 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 6193f5dd26 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 7320c0cd3f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new faaf5f43b0 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 299c582ede 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 993b115b22 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 929319484d 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 350da706b8 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 5066fb313e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new e174788097 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 55fc70e4c6 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new ce45adb96f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 60bc8a2f49 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 9028810ff1 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 610ae301e0 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 42bc336063 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 04ab8a6f94 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new a0dcee458a 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new ef86eb8852 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 6261e687a5 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new ff8b1ddff7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new b09d07c906 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 9287fbea82 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 4b1430df16 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new e0f25d9918 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d3df675331 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 69c0b879bc 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 57ef9ad8f4 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new b7d0191ea7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 2cdf838b6c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new bf7b31b0f1 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 2dd86984f9 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new b4730f2334 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new d83f8a304f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 77868cffe4 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 9e22b66ef3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d32ba8f931 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 3e37e78f29 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new fa61b1c6ea 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 142219ace4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 7375828578 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 74703626b1 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 10956d7297 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 8effd8eb97 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new c3bbd88837 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ab51bf550e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 76730a2ce0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 2ddaa5e929 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 4e22e72438 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...]
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 (243b1b55d2) \ 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 1744 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32568 -> 31756 bytes 04-build_abe-stage1/console.log.xz | Bin 93588 -> 91620 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 236960 -> 236208 bytes 08-build_abe-stage2/console.log.xz | Bin 225820 -> 224168 bytes 09-build_abe-gdb/console.log.xz | Bin 39564 -> 39152 bytes 10-build_abe-qemu/console.log.xz | Bin 31416 -> 31144 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3104 -> 2632 bytes 13-check_regression/console.log.xz | Bin 6716 -> 6248 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 73 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 - sumfiles/g++.log.xz | Bin 2661204 -> 2653400 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2276408 -> 2222384 bytes sumfiles/gcc.sum | 2646 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 902896 -> 895096 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214000 -> 214036 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437472 -> 435008 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 1571 insertions(+), 1789 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