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 aa3d7068fc 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 9e991b76f5 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 0c0acf4be7 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards c0d9ebf088 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards b3500ce306 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 922866259b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards f2040184cb 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 823e0c7711 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards ca426d366d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 63cc03724f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 15fc5059b8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards b04fca9bc9 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards ffa6e1235e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 4442732eed 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 6c9acfe8cd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 16cdb91f0d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards ccbb162927 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards f431909dc2 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 02db615817 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 97ffd84405 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards b8caf49254 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 1ccd03d9f3 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards d435ff305c 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 90b5b4fcc1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 79a97b57e8 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 4e1bf52313 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 1d49ac0e0d 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards b074b9f01f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 31442170dc 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 9aa4163b42 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 28f16971df 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards f6230089f8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1b6bc9c4f1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 3171914a05 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 4a7f039bf5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 7412a6319f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a5d8bad8c3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 0d83e35265 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 69242ed0c0 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards c69b794c5f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards c6fe9aac53 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards abdad8e814 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards c3b7cbffc2 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 18ce260883 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 2069cb305a 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 9a5648f13f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 5488c671bb 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 5e94bb3777 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 25503933fe 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards a5309b2237 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 4b2ab07b57 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 3fb7d0507c 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 74141bf4e0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards b9066a494b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards f496a81c39 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 27b0c61ba1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 60cb7ec3d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 5e05ab1e24 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 54ef50d73a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards fb24ed3ca7 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards fe066a4b56 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 46ffed4c75 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards d7943fbdf5 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 7ac38471a6 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards aa19d60b6f 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards d2d784ebaf 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 9c696f641d 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 9e9b83d528 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards c46182308b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 019a3027fe 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards b944766563 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards eb39951e26 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards b7c76f8ce9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards da168d2335 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 563ead932d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 4bb6776fb9 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 005b68faf8 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 0b656b74b9 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 45b1dd2ad8 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards b5265fb350 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 39aafb65c5 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 60e2e898f7 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards a0e626d782 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards b23bb85185 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 490e9dfb86 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 007b2180e9 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 934d3e06ce 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards ed4fd0204c 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 22dfad6bf1 208: onsuccess: #2012: 1: Success after linux: 12 commits discards e9b8053f29 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 980a98c9b9 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 7dc863a353 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 22f14bdcaf 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards fabd7b44b4 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 60af1ec950 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 8b748d1bd3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards b40be70a78 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards f822bffaea 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards bbf0989bc8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 3e094d7083 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 30d5a06f6e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 2204d6b331 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 15b6c8ee51 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 2728eb5a7e 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new c9caa93833 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 6f2403faaa 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new eafc5bdfdf 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new abf83881a0 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new afabf3ca35 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 0db233536f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 174265749a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 49c0362af5 206: onsuccess: #2007: 1: Success after gcc: 2 commits new e24531fa43 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 5bc1b72d40 208: onsuccess: #2012: 1: Success after linux: 12 commits new beb8feb6e0 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 9da813b7fc 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 29d13511d4 211: onsuccess: #2020: 1: Success after binutils: 10 commits new dbe3dc6397 212: onsuccess: #2022: 1: Success after linux: 3 commits new 6a88a401f4 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 2ee366cdb2 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 2f59f51a4e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 8876152039 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new c811a071fb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 92d679b6d7 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 6acd53a07b 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 7ffe259a60 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 536e294329 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new ae35b06b53 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 42c22c2167 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new d63e95847e 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 6e6c70d5d6 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 9762b0c97c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 5e1d9740ad 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new efdd306443 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 0fc7402dda 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new af69cbff11 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 9723e660d5 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 23903268b4 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 03a368308a 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 5eb943023c 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 40b7ab49ee 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new df4f5e7e09 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 0dbb49f7c4 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 68320742b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new ce3b1ca9f2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 57d71e2e6e 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 70288766ad 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new a67e0a164c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 56ef5310e1 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 98514ee182 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 35f10a12b9 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 1765f88ac9 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new ccaf0383a3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new b834d82c5a 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 864575d512 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 99e746f6f8 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 3e335f8600 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 9603813727 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 441e844969 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new b2218ea26f 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 957615f6b6 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 6a72fea188 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 531b5bf8b7 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 2300d0bf97 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new d8d9f31c95 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 39fc52b899 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new aac594a0ad 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ed6585a8ec 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new a687f6e136 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 80d1805d24 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 79afe9b4fc 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new c40c634dd9 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 2b24a00d92 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 0e4ccdc3f1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new a3f7420a2a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ed9574f025 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new eae1380ecc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 540aad224c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new a62c0cf7d3 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new e205fdf7d4 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8be8c63dd4 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 083204f2f0 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new b00435a6b8 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new fe1a688c0c 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 2196068bfe 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new c74eea221b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new a01dc856a6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new d1f846a241 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 7682f8d567 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new b28b1740c9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new b08841fcec 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 090e881a7c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 6ea53c7f53 287: onsuccess: #2103: 1: Success after gcc: 9 commits new b558ae74aa 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 6930d4da12 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 8513d614ec 290: onsuccess: #2106: 1: Success after gcc: 2 commits new a4a1b54229 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new c1d23be500 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 5edfc09b34 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a60a78977c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4f4a254103 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 2e1776e85c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8c2d29b6bd 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits
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 (aa3d7068fc) \ 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 1736 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31836 -> 32424 bytes 04-build_abe-stage1/console.log.xz | Bin 91712 -> 92008 bytes 06-build_abe-linux/console.log.xz | Bin 9240 -> 9252 bytes 07-build_abe-glibc/console.log.xz | Bin 236852 -> 236576 bytes 08-build_abe-stage2/console.log.xz | Bin 228396 -> 229264 bytes 09-build_abe-gdb/console.log.xz | Bin 39068 -> 39792 bytes 10-build_abe-qemu/console.log.xz | Bin 31116 -> 31124 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2716 -> 3064 bytes 13-check_regression/console.log.xz | Bin 5868 -> 5672 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 63 +- 13-check_regression/results.compare | 40 +- 13-check_regression/results.compare2 | 60 +- 13-check_regression/results.regressions | 41 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 65 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 41 - sumfiles/g++.log.xz | Bin 2673288 -> 2688996 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2228856 -> 2236852 bytes sumfiles/gcc.sum | 2086 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 905436 -> 896272 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214168 -> 214172 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433348 -> 432972 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1205 insertions(+), 1359 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