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 9bbb74978d 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 250522517e 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards e539a011fd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 14138db601 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards d8cba609df 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 0819001e31 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 37adcc72ef 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards cb94a33a18 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards adcc11ed1d 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 1d48055675 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 0a9d1727ed 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards f43c860703 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 660d74a877 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 091c473569 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards ceababf79d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 16480ce205 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards b4ef6f48ed 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards caf631dd0b 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards aea1797e71 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 76f4adc64f 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 29d8d9dc0b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards b5234e8670 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 622861f50f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 04c10cee55 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 6a6903cbf3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards bafeef9668 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 946537733e 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 12491053a5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 7468415e9a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 68e1964a2c 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 471f277760 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards f579a4349f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 5a394ebf41 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 1254069de0 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 8cb1050cd2 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards ff3d55a227 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards b6bf7c300c 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 8e7ef28899 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 39449a21b4 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8ea8e80667 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 6ddc842140 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8b5f6bdabd 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards e7d706400f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 839d8b16c8 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards b05b304932 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 64037bdb24 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4c57743a51 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 9b19f4ff1b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 0fb11a3c34 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 838a4ad713 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 8e8bd68990 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 16c238d4d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards a8e35b21c1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 6a2d9c594b 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 4d6e433642 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 90d5ff791f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 223a57c0a0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards fe5f15b21f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 74820d8684 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards c5640c8f7f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 439e27fcba 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 95c365e8eb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 1470b0a513 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards dd74f9e787 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a04bda0c2a 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6655e6635c 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards d9b63a7d09 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards bbfecb2f84 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 6a55845b1d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards b3ffb3fb91 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 9c6ab60ee7 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 9c921b61c7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 8b645d4d81 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards cfcce096fb 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards d7484a4a3a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ec9112e399 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards ce1ced05c1 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c1d7555396 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 56ca8daa38 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards bdb7f44965 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards db59440d48 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 793f5aaf2a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 06ea65a1b7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 3fddc9da49 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards a781555b15 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 8df32b366e 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 2c40fa75ba 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 420dfc9198 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8e3c6832d0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 9beeb45898 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 0777b018f5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards a15333e8bc 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 550b5edd05 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 2e7b0476f0 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 3ef2d4e67a 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards b0547b8342 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 9ec37ddc15 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 2cbd10b9a7 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards fd6da606c6 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 9b1591596a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 9758d1837f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new f527f532ed 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new eceeaf79a6 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new dfce66f4e4 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 4359fa3ac1 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new abc17db555 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new ee1c76d978 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 2be0dbd399 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 44dea4c5ec 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new a1eceb91b2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new b3da725283 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 897299628b 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 9b38d215cc 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 177649b73e 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new d80a533d19 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new caa6f75db3 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 3ac6d90fc3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new e914c1de20 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 1c5e36f0fb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 8cdb55eba5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 3c32f121c5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 149fba87c4 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 167ecce2be 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 8942763e87 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c8143f39c6 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new c470b14cbf 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new d942fc5fc1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 39f246c4f4 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 2e20b1c7d5 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 9d52ab128b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new dafbfb21a3 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 11bf4a4bae 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 2010eabca0 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 49394b127a 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new f183fa6fb1 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 702cdb346c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 0f0f270235 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 8216cdd2d8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 8c8a96318a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new ae9e9e8019 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 9a208e9207 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new df730e39d7 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 13fe2b2a5e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2096021a21 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 3615186f7f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 0f0803af00 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 895ab8e445 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 9060e92411 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 4f0c52f0e5 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 42a4147555 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 7005ab3d37 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new b57b92d735 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d9b02418ed 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 3cc1b3ce19 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new a4ba67d08b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 0b7af02ee8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 72053d3999 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new ceeba70421 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new eb4ca3c419 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new e633cb381c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 3092a0116e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 0d769c30fa 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new ce9f77e8ab 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new ef590169b5 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 00fd8d3574 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new c97b6acd53 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 26f38be945 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new e0347219a2 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 787c178969 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new a0eccb1e2e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 08bf75641b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 93f6a5d55e 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new bb93c37655 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 41b4fa0a66 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new ad81adb0d1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 1adc9d2d31 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 49355bd33a 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new d808786bac 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new a0972eaa33 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 14962dc62f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 627e110931 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 84433f1953 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new ca55e605f5 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new e473d117d4 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 1ab31d3386 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new a915c8c1c9 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new aefbf6f661 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new d72fada897 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 07f3acb39c 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 5987e19d8a 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new bf38a51cb7 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 72c957acef 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new bb63409c1d 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 4d1e854066 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new caf2679cc2 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 10e9e100be 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 5d7a12c1ab 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new ef48131784 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 943afc2f9b 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 03587c7525 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new ea6cf69318 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 8eda40984e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 4fa65b5ca0 403: onsuccess: #2657: 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 (9bbb74978d) \ 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 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31012 -> 31040 bytes 04-build_abe-stage1/console.log.xz | Bin 70912 -> 70768 bytes 06-build_abe-linux/console.log.xz | Bin 9548 -> 9040 bytes 07-build_abe-glibc/console.log.xz | Bin 245796 -> 244184 bytes 08-build_abe-stage2/console.log.xz | Bin 202536 -> 202564 bytes 09-build_abe-gdb/console.log.xz | Bin 38724 -> 38820 bytes 10-build_abe-qemu/console.log.xz | Bin 31672 -> 31828 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2728 -> 2740 bytes 13-check_regression/console.log.xz | Bin 7336 -> 5996 bytes 13-check_regression/results.compare2 | 96 ++++++---------------------------- 14-update_baseline/console.log | 42 +++++++-------- 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 3393376 -> 3389664 bytes sumfiles/gcc.log.xz | Bin 3014720 -> 3020540 bytes sumfiles/gfortran.log.xz | Bin 1038700 -> 1033552 bytes sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217608 -> 217596 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431708 -> 428988 bytes sumfiles/libstdc++.sum | 40 +++++++------- 35 files changed, 92 insertions(+), 152 deletions(-)