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 0d61c87f15 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 3cc67f20b5 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 9e4bfe5605 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 097cdec36c 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 3a1061fa74 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 5e37f43609 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 9cb605dfb0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 1b243cd2b5 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards bb7316f432 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 45f1fd00b7 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 4bfc28bf21 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 843e2012ca 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards ce68fe62d4 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 7d3bce58cf 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards e99ebdf6c7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e1bb48bda3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 1a0eb2728e 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 498011579d 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 6713a30003 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 56d84fff6f 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 3080fa7b9c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 514a313a82 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards e91dddbc8e 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards baf8a79124 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 7fd3418a78 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 18750f483f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards fd3fab85e9 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards e7c591e7ed 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards ae62eb96ac 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 10f30ef743 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards e56126d3d6 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d46520697f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 5b786495d6 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d2e037e8a0 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 66b60d73e5 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 33a636d30a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 20d16cd8a6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards d0f574c76d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards c94109f036 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 48be0c0e4d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 83cf579b9e 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 85f6072f03 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 64e2070119 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 1e93a11d63 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6b80883ac9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards d5017c088f 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 4fefd8f5cf 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 135f8399b6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 9f63c5e2f7 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c4c0260c69 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards da70f38adc 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 8502893bce 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 72ae828477 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards b06acb6907 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards fdaf7dbc71 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 2d156fe24e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards acaeee90fd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0a4835e9a2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards fe37807f8b 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 308c83212b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 969182524f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 370b991b8a 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 9983973ef5 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 9e58aaf575 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 455be250a1 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards b453ed34cf 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c69e853514 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 1746986177 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards d68c7e05e4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards f748a53de8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 7075e1e742 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 22ade3e09e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 03c2d317e4 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 93dd8f21b5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 5baff176ff 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 236b698d0f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards bb90a850ac 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 259d74278e 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 5a5f7a6200 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 57458e7697 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 7dcd250135 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 0be06ec343 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 975fe0f8ef 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards e8096f8198 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 648ce6c249 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards be471f3fdd 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards cfa40e8ef3 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 7f326203e7 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 9873c0695c 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 448fec9661 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d5cc9e744d 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7bf4687a75 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards f750099fc6 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards f5a95df6d6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 5c17d744b6 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards abbf6d60e4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 6d88fd1c36 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards a94c89e11e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards b9783be7e5 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 567016d4cb 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 52dcdeddc8 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 639c0ff4f3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 1e2ee87395 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new fe8a455cb4 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 92f808a1d3 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 79b0b6d80b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 71d01825b2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new f8a0ca15f1 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 80e4c67a38 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 5f0c19c26d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 5d7ea04292 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 62af13452c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new c2ecb0aaa5 292: onsuccess: #2541: 1: Success after binutils: 13 commits new a6716a06bd 293: onsuccess: #2542: 1: Success after gcc: 5 commits new f0eb80c855 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new fee9833e92 295: onsuccess: #2545: 1: Success after linux: 10 commits new 761790fac4 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new c9fc306fee 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new e6fe120172 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 2c1b9a958f 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 2924af6f4a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new bc63ecf88b 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 7897de9df3 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 8d74fc9fbd 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 246c910b05 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new ccb84e8ae4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new a73478d0ff 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new c61f3a20da 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 6759d95281 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 0f8e4151f6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 7c252a462b 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new f20eebd32d 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 939efe0a46 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f69c415576 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new aa8f5e2ae5 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 019e81883c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new f727e54ae9 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new cd2d698900 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 1ad46d25f6 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 71527eed1a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ca7fe30f91 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new fcf63a965a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new a725d4a64d 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 4426b7eeef 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 2d052e6cee 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 268a2a2167 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 7107ac89d0 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 63c4281419 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 77f2ce2885 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new fe0781c137 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new d57a919f59 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 7da9f25c06 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 2ef74c24e3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 59d6911bde 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new feb8364e1a 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 09da99620a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new e2cca73ecf 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e1e3730d6e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 90fb643e51 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 3fdd78a000 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new bd0895ae3e 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new d94c37c221 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 98b3cb9dc4 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new c9e211c6ee 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 14613dae91 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new a76da63995 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 5f288eea3f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 46c040c303 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 21a1e52939 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 6fdf1a5ef0 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3fd8b58d49 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new accd019e91 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a728eb82b8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new fe19fa3390 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b03b3b5465 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 5414f095c3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 3148e4a52e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 96cf3279fa 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 27c1021ac4 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new fc4391b706 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new b588f3b040 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 941afc7c2d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ffd66daafa 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 678cc02ee7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 658bdea025 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 4cbe0212fa 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 8fe6715de6 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new ae8b8d1baa 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 4616df6ffc 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new a073acc309 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new fc3475edc8 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new c51659580d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 07d69370a3 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 9ff20934ef 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new de3f4162cb 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new a9892a0296 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new bbd107bf72 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new ff9fd328b7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 307a140ed9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new bddce72e7a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 6a46a6c2a3 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new acf8a3b69d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new bdb4666bbe 382: onsuccess: #2633: 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 (0d61c87f15) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31476 -> 31680 bytes 04-build_abe-stage1/console.log.xz | Bin 73092 -> 73280 bytes 06-build_abe-linux/console.log.xz | Bin 9356 -> 9204 bytes 07-build_abe-glibc/console.log.xz | Bin 244432 -> 244764 bytes 08-build_abe-stage2/console.log.xz | Bin 204508 -> 204684 bytes 09-build_abe-gdb/console.log.xz | Bin 38628 -> 38764 bytes 10-build_abe-qemu/console.log.xz | Bin 31500 -> 31444 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2832 -> 2912 bytes 13-check_regression/console.log.xz | Bin 6328 -> 6468 bytes 13-check_regression/mail-body.txt | 98 - 13-check_regression/results.compare | 2 +- 13-check_regression/results.compare2 | 38 +- 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 | 100 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 3394400 -> 3391748 bytes sumfiles/g++.sum | 37 +- sumfiles/gcc.log.xz | Bin 3017664 -> 3024228 bytes sumfiles/gcc.sum | 4068 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1036072 -> 1035136 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217432 -> 217544 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434728 -> 437016 bytes sumfiles/libstdc++.sum | 44 +- 40 files changed, 2164 insertions(+), 2355 deletions(-)