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 29daacfac7 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 12bf2ecaff 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards df8f18ad44 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards a98bf90d05 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards eca1755f5d 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 951087f462 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 4002bc69a2 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards b87e5f6976 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 28b396a326 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 5ac46ec294 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 89057eeba4 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards f0c62e5c88 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards a18930b35b 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 7ac3f665f9 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 6b5126985d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 559dc9ffe9 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 11f18ee3a0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 0ac7453678 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards cefca7c0b2 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 6be607dd0e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 97dd8f82f4 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards bebcfad6e5 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards e991c4070f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards da723a0f91 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards d918cf2109 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 50e309816d 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d8a7f7d5c6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 58cb326856 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 350d4ce092 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 2604cd56cf 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 823271677b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 9dd040e11b 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 3c22d88081 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 547c27c379 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 25baf30a02 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 7e98587dba 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 88000e99fb 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 467cb680f3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 07e9ccad57 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6ff6055e7d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards d29e3fdfb0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards db5f0c9549 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 8d2d43e6ab 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards de187fbec1 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards deb48f06b3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 4fd53bde1b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 44f1259fa3 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 4d4b261f58 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 59d0f2d611 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ec12fdb773 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 4045493863 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards ccaa5e9071 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards fc14c06a92 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards f68a16ab50 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 723b939c9f 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 522eecdbdd 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 2a937c7371 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards fd0a783601 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 9937177fca 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 5bb89566de 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 89d60a9cc4 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards fe1138ba65 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 64b4c95ed9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 724a2f4687 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 3bbd8d7967 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 26ca8b158b 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards c98ac8b836 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards ea802868f1 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 10da70081a 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f008acb291 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b304851515 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1bb729612f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards c7ed8a5814 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 8904c87fbd 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 7b8de92c90 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 7b414fcf1c 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 49df0c7581 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 113a5c29b8 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 7bc1eb7d38 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards f7f3044d3e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 5bafcef8dc 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 18e702b6fd 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ef946de28d 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 5ffeb496a1 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 5349eec945 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 0ccc57a845 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 4729294ca2 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 14fe3acedc 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 01b8a07ae5 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards ca4cb08bd1 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 26b19ed8a1 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards be8dcfc431 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards ca86e625ea 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 87b510ab37 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards e0521dccca 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 014db0bce5 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards b389340dfa 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 57713081a6 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a2e00a964f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 9d5cd4df54 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 864576a440 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new ffe4f0e8f3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 9e8a81c8bb 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 77cafdd571 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 8490e8fef4 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 957010bfb9 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new b7a5f1ad80 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 78c6b0b1f1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 8be07d7e36 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 8a17f3dd07 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 8f5c25180c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new fb945b285b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3b0511e3ce 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 93541e78fe 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 2caa65044d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7846c76960 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new e7684ab276 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new ff7c14b660 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 98503fa400 293: onsuccess: #2542: 1: Success after gcc: 5 commits new bd7e6a3db0 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 93b0698a01 295: onsuccess: #2545: 1: Success after linux: 10 commits new 2dc5a36fd6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 05ec7a45de 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 3d648ee00f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new c7648a7546 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new e21f39bacc 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new d66c50655f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 95a59120c6 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5beb9cce7b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new ff3b1abf36 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 1a24c4989f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 91bba3ed55 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2bca2784c6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 17cfa4861e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 225516c605 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 5c24bd344c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 21a36d4c26 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 06537ed2f8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f7fa80efba 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 537b79de59 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 8aba5f8e62 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 16b0346016 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 237f0a7a4a 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 07668ff67b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 0a6fce67cd 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new fa31834a95 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new a15c7657df 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 11a9c5bd91 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new ec47218423 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 0c44b2f2d4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new ed9e14f66c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 174d84ac91 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 621e170830 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f2c3cb560c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new ee6d6af68f 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new ec68d4aa26 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 6f5bb33f68 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new e53a35de2f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 3023359d7a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new dd8fb22cee 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 2cf982ca03 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new fe1f0af1aa 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new c1567d648e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 389685f786 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 9a1db11082 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new cabd4ec729 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new b1afaa51bc 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d3384be5cf 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 51e592a1de 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new cf8dc2fdc7 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 08d75780b6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 162793a9a9 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new c51f73bfbd 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new e8e3d12c7c 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new cd02752b04 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 1530e64968 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 4afe3e4df2 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new de5561584e 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 33bc477487 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 4b966e8a6e 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new d063878bc5 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 8e7ea0086a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new c3da0716a8 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 34893c1eb2 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 9e0619ed00 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 4328d3de84 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 4abd846de8 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 8070271ca1 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new f8255a4ad0 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 7eead10c87 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 51fedb95da 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 41cd12d9db 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b9df3d34ec 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new e8e7af69a4 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 46e270190c 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new f2305c8c17 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new bd68a8d952 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 7027ecfffc 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 037c4ee187 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 52915af2e2 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new dc78c7006c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 43dd46ae8b 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new a1d1c03a8d 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...]
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 (29daacfac7) \ 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 1764 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30936 -> 31016 bytes 04-build_abe-stage1/console.log.xz | Bin 73344 -> 72916 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 245036 -> 244648 bytes 08-build_abe-stage2/console.log.xz | Bin 204244 -> 203924 bytes 09-build_abe-gdb/console.log.xz | Bin 38596 -> 38392 bytes 10-build_abe-qemu/console.log.xz | Bin 31896 -> 31840 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3068 -> 2652 bytes 13-check_regression/console.log.xz | Bin 6872 -> 5620 bytes 13-check_regression/fails.sum | 9 +- 13-check_regression/mail-body.txt | 91 +- 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 81 +- 13-check_regression/results.regressions | 28 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 93 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 28 +- sumfiles/g++.log.xz | Bin 3397420 -> 3391576 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3021244 -> 3021632 bytes sumfiles/gcc.sum | 4386 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041440 -> 1038232 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215144 -> 214952 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437676 -> 433696 bytes sumfiles/libstdc++.sum | 30 +- 39 files changed, 2350 insertions(+), 2552 deletions(-)