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 4e22e72438 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 2ddaa5e929 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 76730a2ce0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ab51bf550e 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards c3bbd88837 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 8effd8eb97 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 10956d7297 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 74703626b1 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 7375828578 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 142219ace4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards fa61b1c6ea 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 3e37e78f29 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards d32ba8f931 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 9e22b66ef3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 77868cffe4 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards d83f8a304f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards b4730f2334 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 2dd86984f9 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards bf7b31b0f1 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 2cdf838b6c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards b7d0191ea7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 57ef9ad8f4 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 69c0b879bc 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards d3df675331 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards e0f25d9918 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 4b1430df16 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9287fbea82 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards b09d07c906 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards ff8b1ddff7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 6261e687a5 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards ef86eb8852 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards a0dcee458a 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 04ab8a6f94 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 42bc336063 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 610ae301e0 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 9028810ff1 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 60bc8a2f49 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards ce45adb96f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 55fc70e4c6 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards e174788097 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 5066fb313e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 350da706b8 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 929319484d 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 993b115b22 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 299c582ede 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards faaf5f43b0 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 7320c0cd3f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 6193f5dd26 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards c8e51f6063 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 001f92f907 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 68ef81b797 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards b19ae65989 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 7a581726d4 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 1cfae1a74b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards b8c1cbc1e9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 0823ddf5e8 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 940579dc94 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 190f779df8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards c9370a7002 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 1fe3bbd63a 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards da03236703 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 8d944e54d4 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 04de9af269 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 3a1ebba2ca 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards c57c9a12ac 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 8f88a4c695 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 0e8c23eb2b 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards dcd32831e3 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 52094bca19 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards eef089eff3 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 59e69cd965 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 67383bce76 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards aff89eb759 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards f33b3de315 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards ee2e09897a 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 0f5d5f63ff 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards fcb68324e4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 2dad194079 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards f78f1c775b 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 2be41f99b9 194: onsuccess: #1995: 1: Success after linux: 517 commits discards f2ca286f0a 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 25dab114df 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 34fc62946d 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 0ae74526d1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 921cf5dc1b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 0442b15452 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards d416c4bf64 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards c6dbd40d14 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 2c5b0f1f9b 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 31b6033f7f 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards bea7233f61 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 3af3b90b04 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 08394a3c6f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 48b019c76c 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards e40270272c 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 01a613a06c 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards fc70a1add5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 2494dbbf64 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 94e79746ff 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards cc1a158998 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 2f87ea4481 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 1c90b461c2 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new e3b56c619c 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new c0cdc35368 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 8ec08dfff9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 828d795c0f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new a9f11ff0dc 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 4d444d81f1 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new fc94377455 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 3b3d339eee 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 774bbae2c4 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 7199725fa8 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new e658e06c83 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 6d189d6b02 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new ed8e6b2119 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 1057186eba 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new bfbb5c7391 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new dfc6e01371 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new beadf34f59 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new a377f15ba4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 84821c17b0 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new c1ddda81e5 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 453445983a 194: onsuccess: #1995: 1: Success after linux: 517 commits new 8e16afbbdb 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new c65bedf9bb 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 759b2a4eba 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 8b559b38fe 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new b58b45699e 199: onsuccess: #2000: 1: Success after gcc: 5 commits new c6b15dd46e 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new dc4af1acf0 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 1fbdef71b1 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new ad10ea7902 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new df70a0481d 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new ca79fd863f 205: onsuccess: #2006: 1: Success after gcc: 3 commits new eacf252eeb 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 802d04cb04 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 3af5b54674 208: onsuccess: #2012: 1: Success after linux: 12 commits new 45086e915f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new a0130a6c0a 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 6b518768a7 211: onsuccess: #2020: 1: Success after binutils: 10 commits new b4316bac39 212: onsuccess: #2022: 1: Success after linux: 3 commits new 65797f0b0a 213: onsuccess: #2024: 1: Success after binutils: 3 commits new a7083267c3 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 104f5c7967 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new d386e0f3ed 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 5d7bba9bb5 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 6463a24a41 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 3aa49395fd 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 175ba9862d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new c6e173eab2 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new d34e564f07 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 1fa374e299 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 3b0fdb2483 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 44f630dec4 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new a6f19cc15c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 9f18528798 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new e71a162c7d 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 6254b4a2b8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new ff040a86c2 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new b5b8ccd7e8 231: onsuccess: #2047: 1: Success after gcc: 4 commits new fc21039b1c 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 964fd45b28 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 6ce74d6d1d 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 5d7a1f790a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 0b903dc1fc 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new eadacc5916 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new fd2d1ef4c3 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 6460e8b673 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new fd5d124566 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 6e42b00413 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 78eb838be5 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new cfc279d386 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 4950d61483 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new f3a24573db 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 460901f068 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 7a2f3163a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 2ab2aa09f0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 4a19e25cb7 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new e4de5503fd 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 167ba1237d 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 01301eb586 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 30eb850606 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 4556aca9ce 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new e4ad7475e0 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 0ac9d493e1 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new da450948a8 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 53032db7f5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f334070373 259: onsuccess: #2075: 1: Success after glibc: 2 commits new db2fea8f6e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 0556ce7c7e 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 25392d6f8d 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 3a542d7e22 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new c7ca64d77e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 2ef7c5d4ec 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 901d47102b 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new fd7a377d24 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 6d643aee5e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 770fc93c51 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new d05e29b1b0 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new b4110478d0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new ba8bba7c2b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e7ca0934af 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new e0c6a47047 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/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 (4e22e72438) \ 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 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31756 -> 31888 bytes 04-build_abe-stage1/console.log.xz | Bin 91620 -> 92032 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 236208 -> 236664 bytes 08-build_abe-stage2/console.log.xz | Bin 224168 -> 229060 bytes 09-build_abe-gdb/console.log.xz | Bin 39152 -> 39148 bytes 10-build_abe-qemu/console.log.xz | Bin 31144 -> 31748 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 3208 bytes 13-check_regression/console.log.xz | Bin 6248 -> 7244 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 11 + 13-check_regression/mail-body.txt | 61 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 97 +- .../{mail-body.txt => results.regressions} | 62 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 31 + sumfiles/g++.log.xz | Bin 2653400 -> 2654108 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2222384 -> 2260244 bytes sumfiles/gcc.sum | 2768 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 895096 -> 890196 bytes sumfiles/gfortran.sum | 104 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214036 -> 214260 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 435008 -> 432788 bytes sumfiles/libstdc++.sum | 64 +- 45 files changed, 1832 insertions(+), 1747 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (56%)