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 c794aaf2cc 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 719103cc5f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards af6025bd00 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 950887c6fd 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards ab73cade52 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 1566774003 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 1afebac187 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards ad5fa50628 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 237b072125 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 62a40a4528 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards cfb60c0844 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 8aec2352a2 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 40fd3c7085 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards f4c5da8d4b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 2474a3cc29 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 5326b90cfb 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 7d7b3f1116 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards bc1d74cb3d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 7ed800b874 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 61b7db5309 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards c97760fdb7 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 26c0c550e8 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 5b0a1502f6 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 7bd38ef3b6 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 776294f058 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 75e367fb7b 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards c88dff5091 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards deab7706ef 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards effd30f8ad 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7864029d94 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 4ecb25d0c1 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards e47e530dcf 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 2ca4c83633 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards d040a31b02 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c7c66e7da2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards e4a14600a1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 23bec928c2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards a0d20cee64 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 5f52851e4b 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards c1539a2fcc 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 8985a4fdbe 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 5441b0a981 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 4bda203e5b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards d3b3c56a4e 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 75e9e2a02e 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 014b5b7d89 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards f6351e5a3d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 3682de5f9f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 803f3c8585 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 6f08e68193 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3750f5798c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 58b19b5a53 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards c8b633d28e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 7ebceadaa8 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 21c339a8a6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards ef464b8683 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b093fc2fc1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 67140bb7ad 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 350f807dea 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 3d91c8d848 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards a77d48524b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards b6b68e6986 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards a0969e6d94 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 039f612359 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 1537c20c54 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 4252a966bc 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 528994ad7a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 4a2f67ebbf 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards d5df9f9bd4 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards c637fb6fb2 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 432a75f588 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 7c80f2d688 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 67bd15af5d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 54e25c632c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 7295401e92 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2772aa3214 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards e93d203ad7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 2fe098a814 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ae56fb0ce8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards a5423d507e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 5d164734d2 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 9dfdfd1507 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 4bd281d0cd 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 186cf06ed0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 16f852d280 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards e2cfeb5247 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 3186582d99 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards a50a875177 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 7052864784 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 8f8771457a 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 754c306916 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 00b50db9b6 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 8913636f03 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 70b91d97c7 295: onsuccess: #2545: 1: Success after linux: 10 commits discards c9e16853db 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards a0663b7f2a 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards c7770a81e6 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards e1756370c8 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards d9e74a8850 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards f06361d619 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 58395eeb1b 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 546ab0ce7b 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new beaf509497 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7eb3c4113d 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new cc7845bb7b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 1e4aa3c206 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 474268a71f 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 37bdd81310 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new d4bee25d28 295: onsuccess: #2545: 1: Success after linux: 10 commits new 996409fa3c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 6ab3b4d853 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 408e5bbdd3 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 9361dfd7ba 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 8a0e90845b 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new bc0a23758f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 5831dfa902 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 66f16d3e43 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 45348aec1a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 783672b473 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new d40edbdc46 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 1c3f95e3d7 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 9370cc47bb 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new af92abead7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new a0847c1ee2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 8ca2554da3 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new d4936d1899 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 0d91e5cd9e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new f0044326c1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new b19b684638 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 34aec20943 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 01a8eb4f6e 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 961bcb3b49 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 6be52e9138 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b770b67243 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 04a00c001e 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 18762ac3c5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new fb4bf2cfb8 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 5c9631f02b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 5fc5ac7efd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 1420032b11 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 7b3a6613ef 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1bf7501c71 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 404a1ce3f6 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 0eef171cbd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new de644cbd54 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new b12ced06c4 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 4cc5c11983 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new bdaba92875 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new b1c38869bf 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 590e8a90f3 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 1f6358a56c 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6f4f4c22bc 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 692fca0f5f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new c3dc250a9b 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 629369e253 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 80d115ae69 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new f633d6d01b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 43a9723a06 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new b9c1ffa4f1 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new c7aea57e16 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 7adaef3cd2 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 81d29612f1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new ea335e27a8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 4d397e48ff 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new f799bff0c3 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new b8e7a964e4 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8e07bd6bca 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 3049678c13 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new bf85c26acf 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new d5e30f6e74 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new a07aae8da9 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 569dc206b5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ca14afee53 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 39bd4e3ee1 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 7a19add44e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new d45dd3da24 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new c03b738489 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 4d5134a826 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 66082b2a12 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 7277a804e3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new bd9dd78961 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new bd40f5457b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new ae0b586ffa 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 7c5f1ee49f 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 9aed45e40e 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 0ec84c9521 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new c4dda4a3af 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new d8be2ed61d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 7f78e5b843 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new dd85c607c3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new c86b273b27 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 8008eddd2f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new d17650f8ad 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 58c3a2d8e7 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 3b043585f6 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 0337abbeb7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new aaf6e78de3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 0ee47d13db 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 50f655b291 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new af442b3d5b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 59cd4129e5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new c522f49c7a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 14527c8a91 389: onsuccess: #2640: 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 (c794aaf2cc) \ 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 1812 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31420 -> 31356 bytes 04-build_abe-stage1/console.log.xz | Bin 73384 -> 73284 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 245144 -> 245312 bytes 08-build_abe-stage2/console.log.xz | Bin 204604 -> 205188 bytes 09-build_abe-gdb/console.log.xz | Bin 38852 -> 38564 bytes 10-build_abe-qemu/console.log.xz | Bin 31592 -> 31952 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2720 bytes 13-check_regression/console.log.xz | Bin 5924 -> 6108 bytes 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 21 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 3409864 -> 3406360 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2995864 -> 3000052 bytes sumfiles/gcc.sum | 4530 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1035844 -> 1033440 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217500 -> 217448 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434700 -> 435264 bytes sumfiles/libstdc++.sum | 43 +- 39 files changed, 2389 insertions(+), 2387 deletions(-)