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 9c52f087f6e8 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 1e803eb14591 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards a8ce467e433f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 0caa70413259 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards c7d97ebf65a3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 4c18bdc13d67 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 256f17b40d86 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards a26d37750d35 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 689a422805d2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 6da47e13570b 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 54b3662dc97e 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 76ed5eec9f81 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards ed0966388b2a 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards d306d2f125c2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 72ecc038539e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards b0e63045a5e4 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards de154c5b9481 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards bc142d5c53d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 922ede864f5c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 04658dfe4969 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 71618b70c389 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards b307045943bc 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 43e2458483eb 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 480c74b5eeb6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 25baf15d7215 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 35eb97a0525d 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards ee376e3ac805 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e7c3a0fabb23 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards bc5dd2b1d976 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 2bd12974a0a5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards d729fbddcc36 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 71573171ec0c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards b9fa2b6dfd73 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 47d361c2d210 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards f509156763be 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 92b49b78a3f6 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards b20ca53d43e9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 30b0c7c4fe2c 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 157003af12af 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 87659d75df98 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 28b8daa71f6b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards a328a6105e0f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 0f33bfd8de3e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 950170986868 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 927258c3c3ea 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards dff6b29ece1a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 57fb2e33e607 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 5a157b06a66a 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 434df638aed3 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards bea4ef7a1f42 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 318a5b81b18c 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards c5d96173557a 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 308f3d6fd77a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards bc1837cb4d12 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards fd0418e80a66 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards b3709dc2290c 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards be211975c160 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 65ada14592ad 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards f7c82d636bac 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 57ed7510e521 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards e04a629d2638 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 70cf7a3300fa 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 895d4812ae0e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 017d95140327 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 3b2d86660ccc 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards ce71224c7b60 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 827b23fe00c2 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards b9e3541547a4 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 9f48f1f94bfa 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 570dca2d0e69 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards da4dfae34b6b 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards d449c700a249 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 8460ddbc4c55 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 24db4e491445 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards c02e30fe3897 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 98b9118af96f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 7e114c080ee1 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards b505af354fb5 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 3a8d752c9b85 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 1141bd9e43bc 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards d216f06496f5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards ca90cebbdc67 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 474fa27bceca 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 6c2b9f94c3b3 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 00682e9ec538 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 0287f253700b 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards c40b1358412d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards a7735144414b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 7ab17d0cfb4b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 7c0b6bfddf4a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards ce9e154f5a9c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 306d97ced349 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 8c71116e27b3 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 53f2e698ce4f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 0d6641a9f9a8 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 6b216478f7e4 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 834b5853dbe2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 1e6b6a6c6676 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 173cc5e09faa 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards ff4a99060321 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards f1852819c17e 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new d9d328dd4295 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new 13f8efdce9c3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 949297093f44 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 087e521abf37 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new fce60882ba06 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new f1caab26f946 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 8fe70621c913 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 557aed00de7d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 782b0a861c57 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 3bcd2ddd2168 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 2f30cd7952f5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 87aeb29cfbb4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 07f95f11629a 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 1b85a6d3401e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 70ac5c540f8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 2bb7da1713d6 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new c4d6fcd741a6 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 74a2f38afb8a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new f85d51b7be04 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new e52ff5a40d9c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 8e0b461d611d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 1f03eebaa63a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new c760ee2f1ee0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 4d95e1873cb6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new a4525588ff3d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new a54962c26825 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 48d81d659860 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new f2d684f883b9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 7a6e49197988 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 8997dd64a562 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 58e7978b4fec 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new dfca55204459 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 1c66d5483cda 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 751aee728426 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new ab3261a100ce 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 17e162ccb739 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new c75f6526e644 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 68b463337535 194: onsuccess: #1995: 1: Success after linux: 517 commits new 8aee78f25145 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 4374d6db0d9c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 857767816d7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new f423f96db3f0 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 96a99b9e88db 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 1f9249ef7bf5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new 24182b270edb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new ee0e1972d736 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new cfc8df138a01 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new ef3d72fc08e5 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 0e9217761a76 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 01cf95ca6db1 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 5e7f83ddc8fa 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 415d902750e3 208: onsuccess: #2012: 1: Success after linux: 12 commits new f9ed18389a03 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0c200bd26576 210: onsuccess: #2017: 1: Success after binutils: 6 commits new a5cf8801b151 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7fcd2d386df6 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4f435973c7f0 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 5c21db3b32ca 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new bcb21ad975f7 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 9a899d7e031b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 4519c9e75bb1 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 82d58a9f9269 218: onsuccess: #2030: 1: Success after gcc: 5 commits new fe4adff0130c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 7c0daa3fd839 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new eda2be0082fe 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 3927f6efd055 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 74eaa9fee734 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new a6c61694ae4b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 99c8883710f7 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 967b33037cf3 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 8ec1bea3978a 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 36155c1568d5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 154bf4888b9e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 6c7cb4c1ad3a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 7a9a36c3e0cd 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 3ee454a94467 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 6174f58f4a8b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new b0f4bd4ec988 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 9355ec31a89c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 469b052efee7 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 7bee930dfb5f 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new b2de80d90a01 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new e2696a342886 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new e4338b3d9e7d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new bea06e2d4b23 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new ab473055725b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 942f774c4937 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 955f7d139512 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new b673af039494 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 2fe9ec9b2cb5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 025a6e8a015d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 5f2a6aac5106 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new c351a9120130 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new d8de88511f07 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 535dd3558404 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new a181683218b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 441728d6c4a0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 54148bc5dc09 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new 034998545881 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new a5c0d7a1f067 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new b9be8c349c3a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new be13f2aa9866 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...]
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 (9c52f087f6e8) \ 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 1788 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31756 -> 31684 bytes 04-build_abe-stage1/console.log.xz | Bin 91568 -> 91740 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 234532 -> 235356 bytes 08-build_abe-stage2/console.log.xz | Bin 225084 -> 224640 bytes 09-build_abe-gdb/console.log.xz | Bin 39104 -> 39116 bytes 10-build_abe-qemu/console.log.xz | Bin 30636 -> 30700 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2500 bytes 13-check_regression/console.log.xz | Bin 5448 -> 5628 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 - 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2652424 -> 2682104 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2271896 -> 2239132 bytes sumfiles/gcc.sum | 2484 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892564 -> 894480 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214016 -> 213912 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 435400 -> 429744 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 1474 insertions(+), 1540 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