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 3ab1248295 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 4dc7040713 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards deb65b5e27 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards a2ae45f55c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 17431d68cf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0ae6157292 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards ce128832c1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 4ecda5260c 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 1e8eab22da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards af8374846c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 85fa3f51b5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 568d006dc9 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards e9e7aef7db 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards f0eba5881d 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 6d378ad050 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 7769594967 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 3c238f91c9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards d52aa71991 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 92a7491370 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 132019323a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 116fe50e3c 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards bc67b2ec52 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 3c8b88c32e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 6cf2d03133 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 35316cff39 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 3545cc6f3f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 79a1147347 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 90dcadaeff 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 99e52672e5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 5fccff3bad 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards af3d515a0b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards c805e126ea 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 754e9b0e68 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 0e2c60fff5 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards cc77beffe7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 440a26dc85 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 58bdc25fe5 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards b085d60698 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 1d767931d7 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 39ad4ff153 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 66d394f377 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 46a2590f1b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 25af2b4bc1 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 551cc94cea 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards d3c0ed87bb 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards f52537b7e1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards c2768b882a 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards af53f5556c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 680c7a52b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards b3ee3061d6 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 32028d7526 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 52670f677f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ca0fc9e6e5 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 25ec2ebc07 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 587696c03c 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 4dd5457991 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e9c6219946 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 835470197b 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 881958081c 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards ab3286ff2e 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 40db2a0220 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards be35b9b3ad 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 2838a69fc5 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards a38cfa88ec 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards dc7de0c314 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards b97bc193bc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards f33da0c49f 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 887df005e0 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards f72d877792 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 5a999bcb62 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 566ff8916d 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 49d5d4da33 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 3d0cbcb9bb 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 9e946f9ed7 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 925cbed3be 212: onsuccess: #2022: 1: Success after linux: 3 commits discards ee3b573ed8 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards a1433cb5e7 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 1806fc53d3 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 32ff99c2e6 208: onsuccess: #2012: 1: Success after linux: 12 commits discards ace8380bbe 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards e3507243a8 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 59d1eacfdd 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards d04d66384c 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 64a3028cd2 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 26f7e79c67 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 7ebb1977a3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards f82793ea22 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 3c3f82eec8 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8ffdb77abb 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards c9ef01b1bc 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards e1f3ef0d08 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards a5205585c9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards f8e4e4a28f 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 89edf5749c 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dafacd38ee 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 0959dea97b 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 0c33a1f9d3 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 00994bd11c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 69e4fef357 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards f75cb0a63e 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards d66660384b 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 4825974e21 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 27fec9c85f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new d7c983afa2 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new c398717762 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 41eb3af501 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new e7b5da4252 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new d2ed7e6f0b 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 57a4bb527c 193: onsuccess: #1992: 1: Success after binutils: 151 commits new b1d638e2ae 194: onsuccess: #1995: 1: Success after linux: 517 commits new 35104207d4 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new eaff03f2d3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 1e94aa9e7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 3c5ca81bb8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 6ea2d123e3 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 33bd8fee69 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 1a99611e6f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 8f277b5992 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new 7e418bb16e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 5b2b70be31 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new ca539dedb1 205: onsuccess: #2006: 1: Success after gcc: 3 commits new a2721c90de 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 13278fa766 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 55e4344ade 208: onsuccess: #2012: 1: Success after linux: 12 commits new 73efea1a30 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 1a571261b8 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 2eb08e9e58 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 505c9a76cb 212: onsuccess: #2022: 1: Success after linux: 3 commits new 51739e0630 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 2bd8e8ee47 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 7114f16ccb 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 013238137b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new b460f25782 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 93cbfde7af 218: onsuccess: #2030: 1: Success after gcc: 5 commits new cf294a9e39 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 1e86141968 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 360a41a7ac 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 7858129674 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 1bb9f05857 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 58b59512fb 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 633170b04e 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 9a579e3b20 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 99f36ca52d 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new bb6087e721 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new e73d830656 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 0691c54a5c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 9f2ee5abb0 231: onsuccess: #2047: 1: Success after gcc: 4 commits new f74babcc09 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7fd1861b3e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 594360ad72 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 07d7b7f7af 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 2bfa65a5cd 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new c2f29f0f7e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 070bcae0a7 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new d5ae4af76d 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 508b112f59 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 1f4740a64e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 862d75da02 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new e6383de794 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 9b24908d9d 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 3129e06acf 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new a6e6706f89 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new bd824bf516 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 5d8ff77027 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 959efe3851 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new ee03965901 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 7c07c8a06f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new adc1db52f3 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d5593e1ed3 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new ebc3d8c0bd 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 3593154949 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 7e7f38b9d7 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 1bb2ced902 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new abd1e0ef6f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 7ce64cb1c6 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 7f99478a9c 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new d0a2dff8ca 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fb68f0a758 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 23b74e697d 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 3d459fc3fe 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 31a83351a8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3cc0df6119 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b292a7fef6 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 561445de82 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new b4aafe461d 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new fd4eaa0635 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new ec2138152e 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 328978c2cf 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9f516865e9 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 8b4452e787 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 6ef5048c52 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 39234e79e9 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 98952bd617 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 13fab3adaf 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 84581d16ea 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 10026f2a5d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5e5f5f5213 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new b5f30b36b8 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 1b5f084072 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 99ecca3ca4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 740ae84354 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 0b0823540b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 24d2f8e52e 287: onsuccess: #2103: 1: Success after gcc: 9 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 (3ab1248295) \ 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31912 -> 31812 bytes 04-build_abe-stage1/console.log.xz | Bin 91460 -> 91680 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 236964 -> 236896 bytes 08-build_abe-stage2/console.log.xz | Bin 228132 -> 228044 bytes 09-build_abe-gdb/console.log.xz | Bin 39140 -> 39224 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31292 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2624 bytes 13-check_regression/console.log.xz | Bin 5604 -> 5460 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 | 34 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 26 - sumfiles/g++.log.xz | Bin 2649532 -> 2685168 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2262436 -> 2227740 bytes sumfiles/gcc.sum | 2368 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893536 -> 892732 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214076 -> 214140 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434040 -> 434140 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1322 insertions(+), 1374 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