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 8598e89efd 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards cf5e8a2c8e 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 349ba56a2a 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards e78b3da941 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 4b803444e1 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards c24e39d9aa 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 2f2aa6a2cd 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 37073c7a66 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 81a03e9163 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 83a7ec5f35 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards e54b36e8b1 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards ba79e50df1 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 2401fc3425 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards bac7a42507 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 9c82bc66b4 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 787b8c7b9a 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards e6ba70f3eb 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 72e05fbb32 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 88611c550d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 196844eee8 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards d688cfc38f 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 83700f91f3 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 9d2d05fca6 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 57f8bbcd04 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards c392af3859 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards ad85111aeb 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards b1f6814199 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 1736a56865 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards a630238472 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards ad2217d31e 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards d2137864d0 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards edafb26aaa 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 29654ba876 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ab84c72246 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 22e75d5261 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards b1380db516 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 45f900ffd2 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards af0759cfe9 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards df79151e82 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 3af15b70cf 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards ae9ae8e725 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards deee0b6db1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards c645be0fea 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards a2008dd789 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 591f649f94 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 9f8047ac46 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 950e61c800 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 534df50b3c 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 630f61d6ef 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards d632fa644a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 3c43a4b16b 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards cc395d778f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards d91f9e6e7c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 958a945629 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards ec0a4e1fd2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards a34393fe78 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 5b27df3c43 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 80109004ee 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards b4b4c803c5 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 4e72ba4720 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 26df19995b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards b6b2df8cd8 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards c92f1f68da 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards fadcdeb26e 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards f4f4d5f85e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards e0577814e1 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards c995c7b75c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 9a7bd88f31 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 7f8849f1a9 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards ba39c30d62 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 79f7ed0be5 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards a66781039c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards aa2386884f 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 40e0b31b05 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 82e37c1d0f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 8469280a8a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards b93683b608 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards c6f5bd49e1 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 46fe0f856c 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards c55700adfd 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 7f980ade7f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a599829817 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c32a6fffe3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4b53a6920d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 429031aff0 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards b75733dc8d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 72eb440e3e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 311273df3d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards f959016128 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 375fe44b6f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 63c4040a8e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d7e786f871 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 5bf65139da 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e099e98279 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3a586d7810 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 27596e0449 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards e1543d1bb2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards b8f8d66765 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 36795c4340 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0daf192ebf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 78422885d5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 4907082bd4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new ce92e1aafd 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new cccc9b47f0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new bf6b40d63e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 351a079a0f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new e70a3cd49d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new f849c1faad 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 05827aa2ef 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9ba80d14ee 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 95cf71b389 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 893cefac7a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 117e398e58 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a410e04cb9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 2694638eab 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 519bfcf2f2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 575f560767 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7a1323cc61 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 8545d3fe74 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new cfbced5c64 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 458805039f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 33408c70db 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new abf4d20fa0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f544661016 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 6f8255714c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new f15b9d2a6d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new fd032fcf00 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 0767b8ed1c 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 1f67d4dfb1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new ab1eaec31f 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4d189abb2f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 74faad58ef 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 509de468e9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 58645dfde4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 66c2788eb6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new b8de4d421a 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new b267b83d48 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 80061ea02d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new ac29abce34 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 8c6350018c 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 5e3a616f0d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ea31de1762 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 900606bf9b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new bf65b18abb 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 657f97b4d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 34c25c36c0 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new bed3888c04 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 113fa0cd67 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new e7bcf64411 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 2375e38acc 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new b93921e24e 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 8598b7400f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 927e311e00 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 53db5619b0 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new f588a86b44 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 7ed8b7bcbe 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ebad69df73 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new cfe8c94166 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 6157264969 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 2664c0d75b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new eb33def8cd 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new d3b56d543f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 808e7a7fa5 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 2677554357 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 293ecac5df 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new ce35863055 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 5a69d444d5 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 11152f89a6 411: onsuccess: #2232: 1: Success after gcc: 3 commits new a4a714d33a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new f65fd67e92 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new dd85d03e51 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new ae71b3b220 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 18022bc7a0 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new de87dbfed3 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 5eecbc02c8 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 7bd8312a08 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 93c959ff8f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 5591e12998 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 76575b9089 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 2d53d767b7 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 4aafe7275a 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 59d6f1ba83 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 938446f50e 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new a903b624cd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 44ca3a31d6 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new c5d9dc2586 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 119d620dcc 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 8dfe9b217b 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new ca74fab321 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 982168b996 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 9c9ee6615d 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 929f657564 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 053588ec9b 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 5f653d9421 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 299f7b8578 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 2257328d24 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new e98bb923b5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 82aae6af3b 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 47cdc66504 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new b8462276d9 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 82e8ed4fe5 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 8ee6bde3d4 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 2b0f1d4a23 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 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 (8598e89efd) \ 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 1760 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30564 -> 30716 bytes 04-build_abe-stage1/console.log.xz | Bin 88992 -> 89960 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 235684 -> 235764 bytes 08-build_abe-stage2/console.log.xz | Bin 225412 -> 226128 bytes 09-build_abe-gdb/console.log.xz | Bin 38464 -> 38584 bytes 10-build_abe-qemu/console.log.xz | Bin 31420 -> 31828 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3808 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2584 -> 3280 bytes 13-check_regression/console.log.xz | Bin 5984 -> 5748 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 --- 13-check_regression/mail-body.txt | 53 +++++------------------- 13-check_regression/results.compare | 25 ++++++++---- 13-check_regression/results.compare2 | 50 +++++++++++++++-------- 13-check_regression/results.regressions | 26 ------------ 14-update_baseline/console.log | 70 ++++++++++++++++---------------- 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 | 55 ++++++------------------- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++-------- results | 26 ------------ sumfiles/g++.log.xz | Bin 2683044 -> 2681356 bytes sumfiles/gcc.log.xz | Bin 2222356 -> 2214272 bytes sumfiles/gcc.sum | 6 +-- sumfiles/gfortran.log.xz | Bin 898236 -> 900348 bytes sumfiles/gfortran.sum | 12 +++++- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216904 -> 216832 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443392 -> 446652 bytes 40 files changed, 148 insertions(+), 236 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