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 f4081000e5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards cf58f3797d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 7f522df2a1 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards cf707acd3b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 818a7b68d6 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 9b2004e307 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 3546a75711 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 8800e28b6c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards dc2a40aefd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 156776ccf2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 5f986987ff 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 0b121544cf 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 126f83dd02 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 0a7e45c2bc 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 61d789fe8b 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 7980a34d4b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 12aea3a0de 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 343bd3ed9b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 946c0b6990 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 77d8a41aa9 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards b7ffacaf11 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards dc921f123a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards bcb9fe3675 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards fe3349b8d0 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 9c7cae1269 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 339573104a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 321b631882 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 17a30f87fb 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 60cb838655 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 43990049b7 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 4c528e440e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 88cada7f7f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards ebd9171b90 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 2290c69d19 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards d0c9499def 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 75857dbf29 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 1b2c50e34b 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 3792b73b1e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 600bed0b6a 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 85ecd91505 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 82e24d5b99 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f91caf36a5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 5890144e72 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 5e97ab0356 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 9e354836f6 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d6d80256d6 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 30601e3f22 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 01769e257f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards a3889ede3a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 14710234a2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 90b0e76da9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 5281c69cbd 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 2bc9beb745 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 37298c38fc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 7c43f3148a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards d493319e35 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards b79cf3806a 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 0e5b061be5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards ec07c72d18 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards a52fa68b52 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 9a014f0765 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 425a4d04e5 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards d0c28a25d3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 42a3470d45 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 349d7a3acd 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 9b715eace0 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 06b0d6bfcc 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 530198ba5d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a1968100ed 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 728d2f8de0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 7562c0e23f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards d41d0091cc 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards a03e33b086 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards fbd8a0b7f4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards d8041f9735 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 7817a34d75 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 7757cc2a2c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 2799535572 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 9a18fd74a2 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards cb1e011d9c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 8304d170c0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 1bbc5f29c3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 55dabc0343 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards a10c399542 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards f9dc9db5e2 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards a065c57f0d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 01c4fbc521 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 88ef18368a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 6ec8d88887 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 85d4fd1d89 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 28aa6a585b 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards a7324e7ac6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 96763de39e 295: onsuccess: #2545: 1: Success after linux: 10 commits discards b2be406613 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 29f1943275 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards feb29ac76d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 256bf33486 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 1ba163af1b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards bb3a03b3c0 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 0b82ab6aeb 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 899d6f0585 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 62bae27e72 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 58395eeb1b 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new f06361d619 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new d9e74a8850 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new e1756370c8 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new c7770a81e6 292: onsuccess: #2541: 1: Success after binutils: 13 commits new a0663b7f2a 293: onsuccess: #2542: 1: Success after gcc: 5 commits new c9e16853db 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 70b91d97c7 295: onsuccess: #2545: 1: Success after linux: 10 commits new 8913636f03 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 00b50db9b6 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 754c306916 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 8f8771457a 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 7052864784 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new a50a875177 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 3186582d99 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new e2cfeb5247 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 16f852d280 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 186cf06ed0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 4bd281d0cd 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 9dfdfd1507 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 5d164734d2 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new a5423d507e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new ae56fb0ce8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 2fe098a814 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new e93d203ad7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2772aa3214 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7295401e92 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 54e25c632c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 67bd15af5d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 7c80f2d688 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 432a75f588 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new c637fb6fb2 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new d5df9f9bd4 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 4a2f67ebbf 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 528994ad7a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 4252a966bc 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 1537c20c54 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 039f612359 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new a0969e6d94 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b6b68e6986 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new a77d48524b 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 3d91c8d848 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 350f807dea 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 67140bb7ad 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new b093fc2fc1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ef464b8683 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 21c339a8a6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 7ebceadaa8 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new c8b633d28e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 58b19b5a53 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 3750f5798c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 6f08e68193 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 803f3c8585 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 3682de5f9f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new f6351e5a3d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 014b5b7d89 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 75e9e2a02e 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new d3b3c56a4e 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 4bda203e5b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 5441b0a981 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 8985a4fdbe 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new c1539a2fcc 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5f52851e4b 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a0d20cee64 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 23bec928c2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new e4a14600a1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new c7c66e7da2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new d040a31b02 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 2ca4c83633 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new e47e530dcf 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 4ecb25d0c1 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 7864029d94 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new effd30f8ad 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new deab7706ef 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new c88dff5091 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 75e367fb7b 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 776294f058 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 7bd38ef3b6 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 5b0a1502f6 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 26c0c550e8 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new c97760fdb7 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 61b7db5309 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 7ed800b874 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new bc1d74cb3d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 7d7b3f1116 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 5326b90cfb 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 2474a3cc29 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new f4c5da8d4b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 40fd3c7085 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 8aec2352a2 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new cfb60c0844 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 62a40a4528 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 237b072125 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new ad5fa50628 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 1afebac187 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 1566774003 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new ab73cade52 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 950887c6fd 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new af6025bd00 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 719103cc5f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new c794aaf2cc 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 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 (f4081000e5) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31468 -> 31420 bytes 04-build_abe-stage1/console.log.xz | Bin 73116 -> 73384 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 245268 -> 245144 bytes 08-build_abe-stage2/console.log.xz | Bin 204696 -> 204604 bytes 09-build_abe-gdb/console.log.xz | Bin 38840 -> 38852 bytes 10-build_abe-qemu/console.log.xz | Bin 31980 -> 31592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2784 bytes 13-check_regression/console.log.xz | Bin 6024 -> 5924 bytes 13-check_regression/mail-body.txt | 51 - 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 40 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 53 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3399904 -> 3409864 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3026312 -> 2995864 bytes sumfiles/gcc.sum | 3808 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1040708 -> 1035844 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217508 -> 217500 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435968 -> 434700 bytes sumfiles/libstdc++.sum | 49 +- 37 files changed, 2014 insertions(+), 2166 deletions(-)