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 8c2d29b6bd 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2e1776e85c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 4f4a254103 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a60a78977c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5edfc09b34 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards c1d23be500 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards a4a1b54229 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8513d614ec 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 6930d4da12 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards b558ae74aa 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6ea53c7f53 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 090e881a7c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards b08841fcec 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards b28b1740c9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7682f8d567 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards d1f846a241 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards a01dc856a6 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards c74eea221b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 2196068bfe 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards fe1a688c0c 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards b00435a6b8 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 083204f2f0 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 8be8c63dd4 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards e205fdf7d4 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards a62c0cf7d3 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 540aad224c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards eae1380ecc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ed9574f025 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards a3f7420a2a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 0e4ccdc3f1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 2b24a00d92 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards c40c634dd9 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 79afe9b4fc 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 80d1805d24 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards a687f6e136 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards ed6585a8ec 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards aac594a0ad 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 39fc52b899 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards d8d9f31c95 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 2300d0bf97 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 531b5bf8b7 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 6a72fea188 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 957615f6b6 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards b2218ea26f 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 441e844969 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 9603813727 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 3e335f8600 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 99e746f6f8 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 864575d512 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards b834d82c5a 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards ccaf0383a3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 1765f88ac9 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 35f10a12b9 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 98514ee182 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 56ef5310e1 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards a67e0a164c 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 70288766ad 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 57d71e2e6e 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards ce3b1ca9f2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 68320742b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 0dbb49f7c4 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards df4f5e7e09 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 40b7ab49ee 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 5eb943023c 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 03a368308a 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 23903268b4 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 9723e660d5 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards af69cbff11 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 0fc7402dda 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards efdd306443 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 5e1d9740ad 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 9762b0c97c 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 6e6c70d5d6 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards d63e95847e 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 42c22c2167 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards ae35b06b53 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 536e294329 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 7ffe259a60 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 6acd53a07b 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 92d679b6d7 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards c811a071fb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 8876152039 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 2f59f51a4e 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 2ee366cdb2 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 6a88a401f4 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards dbe3dc6397 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 29d13511d4 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 9da813b7fc 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards beb8feb6e0 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 5bc1b72d40 208: onsuccess: #2012: 1: Success after linux: 12 commits discards e24531fa43 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 49c0362af5 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 174265749a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 0db233536f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards afabf3ca35 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards abf83881a0 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards eafc5bdfdf 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 6f2403faaa 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards c9caa93833 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 2728eb5a7e 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 15b6c8ee51 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new f71d872115 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new a27a2233e1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 34206ef602 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 38635ae990 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new a71a0922e1 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new efd7f17f2e 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 633efe196c 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new f860d5a22c 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 2332c03d46 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 3e9d1cdd1d 206: onsuccess: #2007: 1: Success after gcc: 2 commits new b78ea8e1bd 207: onsuccess: #2010: 1: Success after gcc: 4 commits new b334dc3105 208: onsuccess: #2012: 1: Success after linux: 12 commits new 958d6230db 209: onsuccess: #2014: 1: Success after binutils: 12 commits new e8a2cd57eb 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 5f5e4e27c5 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 4e9100431f 212: onsuccess: #2022: 1: Success after linux: 3 commits new ad1259cb99 213: onsuccess: #2024: 1: Success after binutils: 3 commits new a131f178e1 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 5270f78967 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 9a2c4e3cc8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 953ff2b84c 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new a62202d166 218: onsuccess: #2030: 1: Success after gcc: 5 commits new cccf2b586e 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 340bb9bbf3 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new d433b9a7fd 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new db6aef7204 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 528974758e 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 55ec9df0c1 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 2217e2a5d3 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 0132a8b413 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 9575707f8c 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 1c5cf577f7 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 8b5f8af06a 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new c77881027c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new c281c3e5e8 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 1970bbda41 232: onsuccess: #2048: 1: Success after glibc: 2 commits new d59db69250 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new a2e58e1880 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 253ee868d2 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 1d749a520b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new fe36c7f4aa 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new ebbe452700 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new ce50e2657d 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0dbcfda410 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 056c0f07bb 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new be7e7b28ef 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new ed256e12e5 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new f7d1902150 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new af0e963c8d 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 5bf79c9002 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new b1c10f1f7d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 05df599d59 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 5aacb0a437 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new ba51ad1462 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 019fc000d6 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 95db9afded 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new a3b7c7a457 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new bb7a174203 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 9cda51586d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 471c21a465 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new b07eb169c1 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 9aa627854b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new c47b47beaa 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 60713c62d8 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 36afb89894 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 28885320ad 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new f9ff317972 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 0a8d7aa9a1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new fa2b0cebb1 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 98d5cbad6a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 947733905a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 7fa29b4ed9 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new de78b06761 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 038b30e3cf 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 1b11f9c010 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new b354f74b32 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new dce02a0928 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 06e6ca0b26 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8687d82ed9 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 034d534e8a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 3324f1f56c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 0e9575aa1e 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 4888bb7d29 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new c1dbb9eb20 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 4c06d46fdb 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new fa6a421cb6 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 290f741f32 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new d184715fd1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 99ecff02b6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 0047900499 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 39a2fc80c2 287: onsuccess: #2103: 1: Success after gcc: 9 commits new e2dfee2add 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new b2368f2484 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 75da0d7ad3 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 51121b414e 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 85058332cf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new e0940048e9 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 68f39ee1de 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 2f8242ddb2 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8c59968cf3 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new fc80ce4588 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new dc6ff574b5 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 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 (8c2d29b6bd) \ 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 1784 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32424 -> 32404 bytes 04-build_abe-stage1/console.log.xz | Bin 92008 -> 92136 bytes 06-build_abe-linux/console.log.xz | Bin 9252 -> 9256 bytes 07-build_abe-glibc/console.log.xz | Bin 236576 -> 236932 bytes 08-build_abe-stage2/console.log.xz | Bin 229264 -> 228392 bytes 09-build_abe-gdb/console.log.xz | Bin 39792 -> 39652 bytes 10-build_abe-qemu/console.log.xz | Bin 31124 -> 31064 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3064 -> 3000 bytes 13-check_regression/console.log.xz | Bin 5672 -> 5416 bytes 13-check_regression/mail-body.txt | 41 - 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 44 +- 14-update_baseline/console.log | 60 +- 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 | 43 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 2688996 -> 2661488 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2236852 -> 2268964 bytes sumfiles/gcc.sum | 2115 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896272 -> 894944 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214172 -> 214092 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432972 -> 439964 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 1149 insertions(+), 1250 deletions(-)