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 2d3ea3476c 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards c6a1391ede 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 5a2738023b 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards c3565c8fc5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 12f7b39d20 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards ff92e99126 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 5e6e1a855f 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 1286a95170 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards b5a82bdcfe 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards d03f493f7c 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards cedb2af3fa 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 03702841f1 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards aa92ee217a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 7331d157dc 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 1a81bfada1 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards ddb8fe1381 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 7e4fd62517 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards ec3a4d99c7 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards cf31823468 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 752f4c245e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards b47bab5d29 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 73d8a03739 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 588f8b163b 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 301064995d 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards cd3423595c 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 92739d0738 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 23907958ac 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards fac0f83ad0 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards dfccc761b7 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 69677b0381 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 06da950e93 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 8387209862 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards e6ae6efff1 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 3be70c575f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards d7ef7f5953 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 44547ee60a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards bf69a396e1 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 999082b14a 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards a8283cb388 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 186ede1344 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 100709d05d 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 5acccdc11e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 23a89b5ee2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards ec5e282d05 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards ac664f6004 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 9f0cf559ae 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 2756ac313f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b658abe477 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards c5d99b35b9 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards d9632b040b 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 628244b40d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 41ff02cedf 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 45ad928f2e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a5ea0b4000 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 410cf3b8d7 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards a4d29c8189 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 7abdb55548 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards e1784af765 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 051237b056 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards e9ce11e55f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 0699994b67 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 229d7b63a9 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 470560ec28 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 2f9d0463a0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards b8dabb086d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 558be9a29f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 27be59b779 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 977c5ef52f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 04634018bf 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards b23f2f9dec 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 09ce9c7e3d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 8fbb67bcd7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 1469097bba 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 236852b912 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 5a3cede3a3 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 24ba9c1536 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 0c9ef3017e 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b2a2550fe6 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards c7669831b4 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 62f281eefd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 970f89bdb3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards e89e168a3d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 378b4b7f9c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 732bdd9a62 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 1c23e8639a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards db0a76a413 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 4ec3a845be 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 482c9c3fab 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards dd0eb6bdb7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 301b1c558c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 7a95e198c9 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 0458ae8e73 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 8fe5a890ae 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 3d45a33dd2 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 4b98ab8089 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 53fbbd2a68 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 8e21d9f63a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 00a4e8ed78 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 621fe62713 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 8b88bc5dc7 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 5a16afe1b6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 81c2973e5e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 9052b08730 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new a8fbaef93e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 76b2bbe632 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 6fbcf2226a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 5b6fea88a0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new ffa8c73178 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new bc38bf2e76 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new de051418ac 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 5245d85976 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 6c8f6765c9 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ef5078afc5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 072fc47d84 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 9f8b08c402 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 745950a0b7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 320550dd4c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 0386d4b588 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 74c49c9eac 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 8d6d652db7 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new e871d98eb3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 233a510c37 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 1e82966a42 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new dc8fff733c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new a080c403fd 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 6ee9dd5af3 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new fa48d7f261 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 1a72120b39 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new fa6e678d39 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 8b80612894 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 63275dd9d2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new aa3307d004 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new d67a864d21 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a0e37a8a5c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 5ad894c32d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new bcb5ddb7c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 00a78d2e55 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 25970e42b5 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d5dc827ad5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 16d12fd69f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 9e0e861d88 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 0fdc828143 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 941bd5d4d1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new af238fc234 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new e4c267bc73 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 51a223c08a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 9e1cbc7c93 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new e3d24c611f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 17d9a270ae 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 69cb8bc507 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new e4fd04410f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 261c9f428d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 6422e052e4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 1865f58ef8 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ebd39e0eb8 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 36a438e62f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 6136e71223 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 1aee1b9e8b 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new fb1c76ed15 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 95505b8a5a 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 70d52138ac 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 5e96130e72 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 9bd58c89fe 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new f779a4d6fb 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 325c86ed16 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 435f8ac95f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new c9aa1577f9 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 932ecfb439 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 5f7c43bc56 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4c1b1703ff 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 17fb9b2f18 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 30fdb97d78 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new c9deac73ff 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 756d04e585 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 2c46439540 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 91f72675b3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 99efbf15fe 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 8d8a0a52df 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 40a235cb5e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 8518752b1f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new a96f6a3c70 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 839bf36ae1 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 690ce18474 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 8db90e421a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 97d8dd16df 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 6b68c4fb53 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new dbbb5e2ea9 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 6c515910a5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new a722eba673 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 2ce9855f77 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new c6a29d0c1f 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 9450f61c65 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new a6acf73eb3 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 4a2c5165ad 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 1ba2a7b5d8 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 0352032c78 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new b17b0c8b7d 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 76c823ec37 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 7295524281 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 6e356d97a2 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 43c2407d35 408: onsuccess: #2662: 1: Success after linux: 11 commits new e938819d9e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new eb197ece7b 410: onsuccess: #2664: 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 (2d3ea3476c) \ 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 2780 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31040 -> 31092 bytes 04-build_abe-stage1/console.log.xz | Bin 70724 -> 70544 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 8336 bytes 07-build_abe-glibc/console.log.xz | Bin 244420 -> 244324 bytes 08-build_abe-stage2/console.log.xz | Bin 202260 -> 201856 bytes 09-build_abe-gdb/console.log.xz | Bin 38808 -> 38984 bytes 10-build_abe-qemu/console.log.xz | Bin 31508 -> 31528 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2596 bytes 13-check_regression/console.log.xz | Bin 6008 -> 6180 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 29 ++++----------- 14-update_baseline/console.log | 64 +++++++++++++++++----------------- 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 | 42 +++++++++++----------- sumfiles/g++.log.xz | Bin 3399624 -> 3424304 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3018552 -> 3009012 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 1038792 -> 1040824 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217580 -> 217724 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435816 -> 438344 bytes sumfiles/libstdc++.sum | 21 +++++------ 39 files changed, 90 insertions(+), 112 deletions(-)