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-aarch64 in repository toolchain/ci/base-artifacts.

discards 63b4dffbe2 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 73b6220748 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 1d787dde82 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 4b1f423990 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 0637aa9ed2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards b9803a1a52 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 4c6973a4b3 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 806f1a588a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 59dd5e9643 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 72fd7880b1 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a15c8bf243 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 83220d5c93 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 924e9245e3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8ecba244f4 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards e6f969f474 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards a504d83d50 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 9cf6c6e6b6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 6a7207caaf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 25d404ff44 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 2cc990d9d7 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards a42e763cd1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards fc97bdddda 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f778c1ebe9 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards d593d594ff 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards cec7dc749c 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 8b1d22ea6f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards d786ba5f0c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 83ebdf2487 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards b93b13b708 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards a55a051fb0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 251307ffb7 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 151f129827 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3f4a85844b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards aab6a6165d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards a9b1b2e839 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ac4ade9dde 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 58c74bb442 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 6aa80e3fca 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 7c902410d8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards e1d8c38b08 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards b62210e9ef 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards e9c4dc68ac 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0789719136 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 2d3f89760f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 4d9082c622 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 6a790cb4aa 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 7cea8ba0c0 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a66a9c29a7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards d43fd28383 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 12c629aa54 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 657e2bfeea 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards fe62c244f3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 4e0cace94d 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards cecd43f41e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards bc4be1c426 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards ec22f44d52 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 65aa7dcee2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 2a70a18ac3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards a38c64c99c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f7525a2b68 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards f87af8513c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 103dcd0bfd 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 2c6ae251b5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 61159ea233 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards c94ca044ff 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 7e616a4f9d 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 6d9daf7f1a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 83b38ffdd3 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards aa158d2f78 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 602cc294fc 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards a1b898f1b1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards e17d12ade6 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 7dffc805c1 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 7564e1ac7d 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 19e92ff14f 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards b414cbfe0b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 79a314a901 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 82efaf916b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 967b2dd7e4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards c7b7480b43 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 328690c814 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 37b5d8543c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 47faf6fbc6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 7bce49929f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 91b9b503a0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards b86d339739 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 73f83b6a06 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d72e3d184a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a52f502b67 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards d5496b9c53 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 088629361f 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 9693c0bb0f 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards d535607de3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards f9e3d24cf4 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards ebfa6ee9a0 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards cbc1282bb1 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 0f20965d56 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 980f46516f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 620c385c36 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards caeb9d7bb3 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 31c02982d3 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 8e7ceccbf7 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 9ca2a906d9 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 5d9ec1a180 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new a93ede66b8 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 01c44959a9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 7abc0e5ad7 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 0207af601a 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 98eae9c21d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 8a40ab6cc0 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 384cc6b71b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 38b60f2420 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new faf4bfd930 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 9a534f18ef 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 42a2493397 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 77836fcec7 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 9d335e6ce2 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new b208ca0071 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 7790f17b10 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 682d8c07f9 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 812d408c8d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new f8503eaab9 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new ac5ab539dc 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new a087d44965 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 5c9feda291 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new c3e12d231b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new afa344a2bd 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 536af120a5 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 08f5763c72 293: onsuccess: #2542: 1: Success after gcc: 5 commits new dd84a08a53 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new ec4970c2e1 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1bef30a2bf 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new edc8248c5d 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 7c9f6707b9 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 2a516479b2 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 2b75fea674 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new ea26126ba8 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 0d7b11d6ea 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new bd064c5767 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1c85069cb4 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new ace93e0495 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 18e047d16f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 0acc3efeb1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 632a73230e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new e66d0dbb98 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new f3bd6cc825 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new e59df08f90 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 026e72700f 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new a89c6afe92 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new edb4cbab05 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 13711f7794 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 910b69a593 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 53fe9841fa 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new e8b8ba723e 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a57dcb236b 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 08f9e66515 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 6eaccd4f63 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 2f51c82ce7 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 2e89d5dcbe 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 53786bad30 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c8c64a380c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 15f72c2c46 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 02b5f9d8f6 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f374c77bc0 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 055e77c547 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 4423746035 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e0929e62de 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new edb6041721 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new e8032627fd 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new d52935a390 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 55374fc788 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 58f441bf00 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new aa75f70b83 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new dba8a2b78e 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new ae616a234f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new d6e8be334a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 486c40dfb4 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 39628bc63d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 811e8fd3c7 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 490b8df7cb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 77c56de7a2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 1c33fe8285 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 7091609600 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 1414072b47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 965d67dd56 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 50ac4f1f51 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 517f0b0bfb 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 3089d64b83 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 4b317613f2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 148aabfcd8 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 541d7103a2 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new cf2bd45468 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new c0840f6abc 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new a37000439c 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 1b1239f83b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 959e79d8b0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new f86257b9bd 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 0b41297312 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 955551e177 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new b5fabd00a3 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 894f66ccea 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 44d0ee8a4b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new edaaf326a2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 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 (63b4dffbe2) \ 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 1808 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31112 -> 31612 bytes 04-build_abe-stage1/console.log.xz | Bin 72932 -> 73744 bytes 06-build_abe-linux/console.log.xz | Bin 9012 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 244468 -> 245628 bytes 08-build_abe-stage2/console.log.xz | Bin 203912 -> 205368 bytes 09-build_abe-gdb/console.log.xz | Bin 38244 -> 38568 bytes 10-build_abe-qemu/console.log.xz | Bin 32104 -> 32524 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2676 -> 2728 bytes 13-check_regression/console.log.xz | Bin 6128 -> 7468 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 32 +- 13-check_regression/mail-body.txt | 123 +- 13-check_regression/results.compare | 64 +- 13-check_regression/results.compare2 | 198 +- 13-check_regression/results.regressions | 64 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 125 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 64 +- sumfiles/g++.log.xz | Bin 3387504 -> 3401080 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2996084 -> 3034708 bytes sumfiles/gcc.sum | 4278 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039500 -> 1042600 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214992 -> 215088 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431024 -> 436292 bytes sumfiles/libstdc++.sum | 616 ++++- 42 files changed, 3142 insertions(+), 2573 deletions(-)