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 d7a5aab069 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards d434881d5a 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 383de783b8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 6831eca453 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 14d00bebf0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards ee79018f54 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards c8e975843c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 895bf61fa3 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 833b590a0c 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards a45a6527e2 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 11ec42187c 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards efdedb6b3a 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 4ba2134d65 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 421c10ef28 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 19c35eb713 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards f444f8e115 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 8c19aecb5f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 102685aa3d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 8354945187 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards ae92d746be 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 90f64881cb 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 2f8ff60d36 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 0329798736 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards f61b4915b0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 608c880703 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards a91dbddbb6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards d2d8280934 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 9268bec60d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 436eca2a8e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards d7cabcf3be 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 938449341b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5c521c4c64 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 8a9866c86b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards db7a3f1210 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards f43b5e0614 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards b78ee4a22a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 5ce3cc8a75 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 12926d93da 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 61b1dad153 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards a24f0268e9 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards ff6709633c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 1fe5a5d902 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 10d066c25e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 20e81f4b43 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 8be1a1410d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 6c935e3d59 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8f1c7d85fe 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 2222610dbc 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 5d367f2e6b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 365b0bb60c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 3a048e8abb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 42f74fdb65 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards bd7c468915 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 1347cfd6b5 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d5252ae098 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ad2ff64883 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards c76a9efc94 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards a6478b6dfa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 45c9c5b0e6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 40e41292dc 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4451f22a03 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 153d049f64 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 7765c8a085 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 90f93b0fd8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 46a1fb973b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 4758f700b1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 98dc1cb1bd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d910cf8d84 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards e63e92f7cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 42207d26d9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 98aa41c4c6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards fec1a4293a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards e92a3aa2da 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards bd2c7b5902 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards e2961bb399 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards cbc2206f4f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards dc03f8cc8a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards b01e77a4bb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 40a2400cb6 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 3db76ddf71 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 03068d827f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a00d7b37d4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 5dadeaf4b0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 84d115d94d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 15e18fbacf 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 4875dd39c3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c339429b20 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards fed2c5951f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 95f74b33e6 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 43a0a56f49 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards e9e19e03ec 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7b2f84f495 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 653321eb32 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b94152a645 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 438c4d0a06 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2883728061 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 60ca485452 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 699edd5ecd 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 2c48f3ab37 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 364b047d38 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ea1404c521 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new c2ad230567 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 0e923a6869 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new f8df813beb 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 3e651ee97e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 798088780b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 5f0a4a7d66 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 143561e8d3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 79cf774821 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 57be9ef200 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d655042b70 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 3081390de2 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 841555d0cb 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 550bda28f0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 6a6ddeca5f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6423410919 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9216a9a262 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new cc99ba9853 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2d52abe172 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 198e70206e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 106bfa2b59 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 6a9e6f27fb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2b795fc724 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new c3b833edd9 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 183b69e39a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 688090a82a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 64c4578f1f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new d4d19635c7 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 94e80e3afb 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0580e33dcf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 9093b550fd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new d89a4feb5d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new d4880e3be5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 3d48eb87fb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 97ebe1a32a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 94b950a0ec 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9699789ef5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new a9f1d8f908 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 6b01c1bb82 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 695705ddd5 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 1ba980383d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 12ab00ef45 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 55ccd2d957 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 7670c8afb0 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d122b7629d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 732f70675c 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new e09f366da1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 8e14b27e9d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new cca9caf1fd 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new a4d40904e7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new c576036ee3 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 1d60f498b9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 63e7a6c19b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 3b0d8b90ba 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new dffabe1c2e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 77550d7f99 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new cf7f5cbda8 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new d7e455e039 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 65bd718444 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 142fb1c320 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new ad28d14c6d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new c0bef9072e 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new ce3a9fba72 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new a7c0415f9c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 0793f5fb9d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new f0b946d023 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 89992aeb33 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 8c99ce694b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 2fa1e31d9e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new b63b60392a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 403a5a0edb 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 9760832e2e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 56396e6e4a 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b8cbb1dc38 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e17b00f7c1 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 50bb32e71d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 6923dbd250 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 44620aed4d 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 2306f13542 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8c36aed1ea 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 61a675d784 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 9627d86d17 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new d97b627f2e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 2b92351d42 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 231fe25f81 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 5546b82897 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new c0130ad6e1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new e766c358ef 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new ab2755f36d 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 424160bd7f 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 42b14bcd3b 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 9e1caac301 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 4ff4fd4846 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 157133e8cd 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 2219f36b47 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 337df0e301 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new d8276f4514 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 026805f652 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new ac61a266f9 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new e0b146cf62 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 5dde09f6e5 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 6e5eac421b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 4e7bd31901 419: onsuccess: #2243: 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 (d7a5aab069) \ 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 1800 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30956 -> 30932 bytes 04-build_abe-stage1/console.log.xz | Bin 92748 -> 89172 bytes 06-build_abe-linux/console.log.xz | Bin 8552 -> 9028 bytes 07-build_abe-glibc/console.log.xz | Bin 236416 -> 236736 bytes 08-build_abe-stage2/console.log.xz | Bin 228884 -> 225144 bytes 09-build_abe-gdb/console.log.xz | Bin 38448 -> 38852 bytes 10-build_abe-qemu/console.log.xz | Bin 32028 -> 31744 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3560 -> 2720 bytes 13-check_regression/console.log.xz | Bin 5568 -> 9132 bytes 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 481 +- 14-update_baseline/console.log | 62 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- sumfiles/g++.log.xz | Bin 2633104 -> 2630904 bytes sumfiles/g++.sum | 172882 ++++++++++++++++--------------- sumfiles/gcc.log.xz | Bin 2188636 -> 2222728 bytes sumfiles/gcc.sum | 100479 +++++++++--------- sumfiles/gfortran.log.xz | Bin 891304 -> 893672 bytes sumfiles/gfortran.sum | 18880 ++-- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217032 -> 217104 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437016 -> 438192 bytes sumfiles/libstdc++.sum | 443 +- 40 files changed, 146936 insertions(+), 146395 deletions(-)