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 c45faf157e 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 1665cf8fe2 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 8e9adec227 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 2f8ccb076e 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards c223241dc0 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards abdfd39357 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 37a8146e0b 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards b77506ce77 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 5ce422ed52 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 18f5e7556e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 372cb4fff7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards d6bef9a03a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards b9c3d09e62 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 5719e9b68f 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 1d4c215331 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards ca80757b74 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards edf59c921f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 8aad132252 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 6eb9d536b3 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 43669b835f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards afd6568262 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards b2e92f5ed5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 6832aed883 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards b4c9992728 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards a3fefa4873 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 84dff88a59 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 647525eab3 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 6189c891e0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b82d169697 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards ddee30683a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 80cdcc2f01 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards ce938f2e70 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 7f69fba199 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 1cf6767184 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 10f86869cf 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 85fe0b27e9 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 4081bd9997 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 0e203a1699 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 85ff94b1af 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards b3abf6674a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 7079169a19 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards f207c14d37 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards ab956d18cd 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 585f6ec50f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 3ac587245c 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 4aced0f9cd 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b9641fb5f5 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 0261c05707 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards a6098eadda 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 256ebe9f07 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards f60aea8274 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards e0acef8036 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards e977ef4bb0 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 7560a952bb 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 4eaad14073 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 52817ca956 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 0579cfcd4b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 0a554d6a0e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 0280e66264 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards b3b2fa3c6d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards da475cf81f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards d54365cfa0 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 42a0c50cc5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 7d66cdd44a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards a28918649e 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards cf95e7a7fe 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 495d8fbda9 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 4dcfd38ffb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 8df7254c60 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 6d9d47a956 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards c026025e10 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 77152ddb05 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards ea820807a7 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 997c0dc571 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards ea10a0cb21 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 2d37122e35 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 1860a8bd6d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e1612562a0 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 62b8cbe318 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards e99410dc96 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1530b03805 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 75a5f38800 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards aa9b4c091c 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 51acda3c9d 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 2e49424ff8 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 8fdf6ff719 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 07c3a1ea73 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 506e61285c 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 3040f9d486 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards b930c37b13 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 0adfbf4863 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9ddf8de4ec 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 60d291459b 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 6df3af779f 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 1f1859487f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 5f5640f049 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 017960c603 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards a333a0f5c9 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards e5b99d2a04 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards c705ad4209 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 9fd83eb3b5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new babf3f46de 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 5a16afe1b6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 8b88bc5dc7 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 621fe62713 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 00a4e8ed78 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 8e21d9f63a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 53fbbd2a68 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 4b98ab8089 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 3d45a33dd2 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 8fe5a890ae 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 0458ae8e73 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 7a95e198c9 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 301b1c558c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new dd0eb6bdb7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 482c9c3fab 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 4ec3a845be 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new db0a76a413 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 1c23e8639a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 732bdd9a62 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 378b4b7f9c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new e89e168a3d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 970f89bdb3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 62f281eefd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new c7669831b4 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new b2a2550fe6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 0c9ef3017e 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 24ba9c1536 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 5a3cede3a3 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 236852b912 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 1469097bba 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 8fbb67bcd7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 09ce9c7e3d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new b23f2f9dec 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 04634018bf 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 977c5ef52f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 27be59b779 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 558be9a29f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new b8dabb086d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 2f9d0463a0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 470560ec28 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 229d7b63a9 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 0699994b67 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new e9ce11e55f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 051237b056 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new e1784af765 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 7abdb55548 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new a4d29c8189 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 410cf3b8d7 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a5ea0b4000 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 45ad928f2e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 41ff02cedf 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 628244b40d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new d9632b040b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c5d99b35b9 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new b658abe477 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 2756ac313f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 9f0cf559ae 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new ac664f6004 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new ec5e282d05 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 23a89b5ee2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 5acccdc11e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 100709d05d 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 186ede1344 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new a8283cb388 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 999082b14a 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new bf69a396e1 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 44547ee60a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new d7ef7f5953 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 3be70c575f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new e6ae6efff1 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 8387209862 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 06da950e93 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 69677b0381 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new dfccc761b7 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new fac0f83ad0 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 23907958ac 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 92739d0738 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new cd3423595c 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 301064995d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 588f8b163b 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 73d8a03739 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new b47bab5d29 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 752f4c245e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new cf31823468 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new ec3a4d99c7 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 7e4fd62517 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new ddb8fe1381 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 1a81bfada1 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 7331d157dc 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new aa92ee217a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 03702841f1 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new cedb2af3fa 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new d03f493f7c 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new b5a82bdcfe 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 1286a95170 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 5e6e1a855f 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new ff92e99126 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 12f7b39d20 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new c3565c8fc5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 5a2738023b 407: onsuccess: #2661: 1: Success after gcc: 7 commits new c6a1391ede 408: onsuccess: #2662: 1: Success after linux: 11 commits new 2d3ea3476c 409: onsuccess: #2663: 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 (c45faf157e) \ 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 1744 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30940 -> 31040 bytes 04-build_abe-stage1/console.log.xz | Bin 71076 -> 70724 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 243848 -> 244420 bytes 08-build_abe-stage2/console.log.xz | Bin 202748 -> 202260 bytes 09-build_abe-gdb/console.log.xz | Bin 38660 -> 38808 bytes 10-build_abe-qemu/console.log.xz | Bin 31580 -> 31508 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3012 -> 2592 bytes 13-check_regression/console.log.xz | Bin 5756 -> 6008 bytes 13-check_regression/mail-body.txt | 49 ----------------------------- 13-check_regression/results.compare | 41 +++++------------------- 13-check_regression/results.compare2 | 57 ++++++++++++++-------------------- 14-update_baseline/console.log | 56 ++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +----------------------------- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++------------ sumfiles/g++.log.xz | Bin 3401596 -> 3399624 bytes sumfiles/g++.sum | 10 ++++-- sumfiles/gcc.log.xz | Bin 3014124 -> 3018552 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 1038592 -> 1038792 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217504 -> 217580 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439008 -> 435816 bytes sumfiles/libstdc++.sum | 20 +++++++----- 39 files changed, 112 insertions(+), 234 deletions(-)