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 755433d25f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 29b2af5d43 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4d84f947b8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 612821792a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 4dac961ce1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards e9e0af6567 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 35038f6b32 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 20e7b3cd49 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 38bf71933e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 63454d5d20 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 252b85fd90 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards d9b66d9c73 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 4df9b455b0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards fe683e5fca 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f42673841f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 307bcdce39 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 3676d7a201 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards a5690234f4 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards beea0f0ca3 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 0c4ef64826 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3c02207bfd 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards c56c4d2de8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 5deb365816 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards c2a6a93112 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards db68738bdc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards a4c4f00d6d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards d48e33b784 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5fb296b7d6 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 8e158952b4 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 973df13baa 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards d9dc01bcaf 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 681910f6f0 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 06cc24850e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards f026cda932 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 9ae2ddb524 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 02e62cf3b5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 17956c8053 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 5710918412 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5b244c7a47 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 4f7e5c40a4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 571f9a12f7 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards fd47efb0ce 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards f73aca767f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards bcfbb9a1ef 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 31d7320a82 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards be57a965d5 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 7b8204660e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 2800a8f3c8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 824d7b3da2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards b35a9e9050 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards adfa81836a 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c8e8436453 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 3386f98fd8 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards c5902b2693 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 5aedfe07e2 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 2d192ab24a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 608b11dfe2 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 6d5a814d41 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards ed3e64722f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 04ccaf4854 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 20dadbf1ec 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 2c0d0a6032 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 7de0fa2da4 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 3501c33534 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 6f7f71dbf6 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards c932b9dc88 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards eda3f8da8d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 40cf575d9a 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 07b7c5674b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3eb220291d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards e9870c09ce 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d3df1fa284 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards f6428c946c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards cc42d95ffa 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 014f6fab85 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 553f14f3df 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 0a60be4f0d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards cb012e468e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 92dfaf3dbb 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 6503154082 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards d409b57496 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards b739338dd0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 4cc17d6ed2 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards f0f717936e 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards cfd446f14a 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 735b63fa46 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards d9738da735 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards f71bea3b8b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards cb9d7eec0f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 85fad45fa9 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 1734903af1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 70b3fd6235 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 8d97b40b3d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards a76a86ab2e 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 4a2e8a525d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 83f601949e 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e4c1a66f65 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 1d40124d2c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 5e029819db 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 9b12a9c1d7 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards aa8e3fa518 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 4b3444c5b3 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d30ef9f0f4 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 5ce040e8c3 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new f5a4612b99 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 67b978aece 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a9d2cf51de 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new c7849b4a02 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 720a7fef24 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 811b427895 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 6865bc7e4d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 758604b1f6 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new da58a95215 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new f91c408b27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new c9ef6bd819 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new ed990161b2 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new ad75511e77 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2e0c5f95cc 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 674e453358 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new fcd2288fb3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new f5582323ce 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a41650ee22 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new d734421c90 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 57ec7d84e8 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new f378ddf420 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 327291d41f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new a91d84f2ac 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 9a409dce61 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 87396f1106 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 3034683c41 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 684baa0b6b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 27f1ca0bf2 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new af7a04199b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new c318dc14e8 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 79facc54ae 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 9b46f86705 292: onsuccess: #2541: 1: Success after binutils: 13 commits new dd1a9682ba 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 0c28ae3cd6 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 8929221065 295: onsuccess: #2545: 1: Success after linux: 10 commits new 7cc037aee1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new a3e632b2ad 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new fad8954f39 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 091f3eb115 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 5a35300355 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new a0a1f42e81 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new a5ed938703 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new dff555e34e 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 3f7a934757 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new b9541bebc3 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new def064f867 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new ef3709fa52 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 2fb4aaace3 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 0ff12fc58b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new fcdbb5463c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 895a757391 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5c8817db51 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 187f0dcc1c 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 70dd382517 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 5d1b717688 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 7d14bd6464 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new eec346e29a 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new aff609700f 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new c8007f2d36 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ac1b20753d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 481ea271c3 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new e75519b77b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 75a0407cfa 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new a0bb7bb919 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9d5bd24db3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 8f04b19cf9 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5a92355299 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new c7d84bf222 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 82e50668cd 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 9f88cabd07 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 5f0945e03c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 36dcce58c2 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new c329fcef7d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 9c96ecefa0 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 880a5b6b5c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 16288b3604 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ebab885fc2 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 1046618de7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 5edb1de572 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new d40eb145e1 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 7595cac20b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new ddd2be4636 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new fa30c04b04 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 000d212658 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6cc9ca31b8 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d2ae27384a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new ea4513079f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 3ae2817049 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 058f704804 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new e54d42b4c5 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 3bff638b46 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 33fcb0bea1 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8fc4eecf6a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 1e2c733faf 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 53ca3b985c 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new d5ee246575 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 2554367026 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 85a56d2b72 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ae99fcddb9 359: onsuccess: #2609: 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 (755433d25f) \ 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 1780 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 35836 -> 31220 bytes 04-build_abe-stage1/console.log.xz | Bin 73416 -> 72856 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 244452 -> 244996 bytes 08-build_abe-stage2/console.log.xz | Bin 204912 -> 204192 bytes 09-build_abe-gdb/console.log.xz | Bin 42948 -> 38676 bytes 10-build_abe-qemu/console.log.xz | Bin 32540 -> 32276 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3220 -> 2640 bytes 13-check_regression/console.log.xz | Bin 8084 -> 6772 bytes 13-check_regression/fails.sum | 15 +- 13-check_regression/mail-body.txt | 88 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 215 +- 13-check_regression/results.regressions | 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 | 90 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 29 +- sumfiles/g++.log.xz | Bin 3401764 -> 3401500 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3017128 -> 3021316 bytes sumfiles/gcc.sum | 3331 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032512 -> 1036708 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215240 -> 214976 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430692 -> 427600 bytes sumfiles/libstdc++.sum | 31 +- 43 files changed, 1986 insertions(+), 2081 deletions(-)