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 ae99fcddb9 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 85a56d2b72 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 2554367026 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards d5ee246575 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 53ca3b985c 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1e2c733faf 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8fc4eecf6a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 33fcb0bea1 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 3bff638b46 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards e54d42b4c5 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 058f704804 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 3ae2817049 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ea4513079f 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards d2ae27384a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 6cc9ca31b8 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 000d212658 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards fa30c04b04 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards ddd2be4636 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 7595cac20b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards d40eb145e1 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 5edb1de572 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 1046618de7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards ebab885fc2 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 16288b3604 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 880a5b6b5c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 9c96ecefa0 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards c329fcef7d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 36dcce58c2 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5f0945e03c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 9f88cabd07 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 82e50668cd 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards c7d84bf222 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 5a92355299 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 8f04b19cf9 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9d5bd24db3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards a0bb7bb919 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 75a0407cfa 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards e75519b77b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 481ea271c3 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ac1b20753d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards c8007f2d36 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards aff609700f 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards eec346e29a 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 7d14bd6464 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 5d1b717688 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 70dd382517 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 187f0dcc1c 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 5c8817db51 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 895a757391 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards fcdbb5463c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 0ff12fc58b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 2fb4aaace3 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards ef3709fa52 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards def064f867 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards b9541bebc3 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 3f7a934757 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards dff555e34e 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards a5ed938703 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards a0a1f42e81 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 5a35300355 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 091f3eb115 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards fad8954f39 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a3e632b2ad 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 7cc037aee1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 8929221065 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 0c28ae3cd6 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards dd1a9682ba 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 9b46f86705 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 79facc54ae 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards c318dc14e8 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards af7a04199b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 27f1ca0bf2 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 684baa0b6b 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 3034683c41 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 87396f1106 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 9a409dce61 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards a91d84f2ac 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 327291d41f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards f378ddf420 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 57ec7d84e8 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d734421c90 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a41650ee22 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards f5582323ce 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards fcd2288fb3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 674e453358 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2e0c5f95cc 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards ad75511e77 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards ed990161b2 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards c9ef6bd819 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards f91c408b27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards da58a95215 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 758604b1f6 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 6865bc7e4d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 811b427895 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 720a7fef24 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards c7849b4a02 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards a9d2cf51de 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 67b978aece 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards f5a4612b99 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 5ce040e8c3 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards d30ef9f0f4 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 3d626e1f33 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 367e071176 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 755a54b6db 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 36ca46d82e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new d95e83c5a8 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new d89f660687 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 745573728c 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 6dbaf3f2c1 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 559ad33618 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 63a3214fc5 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 3d7991a5b7 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 4e19df0ce2 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new a27de2c990 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 780872024b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 275e5232bb 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2f1d45a9d9 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 4450be823c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new a0dad18183 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 851917da2b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a68ca9a06b 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new a328bb70c5 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new cb91fa0ddf 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 74acd8e260 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 4a48c80af1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 5d5b8e996c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 4c95b0431b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9793e362ab 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 5e6b17807c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new b24aff1296 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new c3195ca5f8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new e970da7027 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 28749f5ff1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 546a15ff18 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 4118f0afb3 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 8b779876b6 293: onsuccess: #2542: 1: Success after gcc: 5 commits new bd423a54e5 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 615be6d9ef 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1d9101c72d 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 936882ee3a 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 3a7bd8db3f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 05cd85d9b3 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new f71d2db5df 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 573dc4bf42 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 74110203e1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new e6bb510431 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new d046ef8b52 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a26660c0d7 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3a4b36fcf6 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 8e9d1c96fd 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 3390a35b03 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c6ca391a84 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 58b08c64d8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 796d4f1420 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new b40432bbdc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2285f61db0 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new bd725d45cb 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 7966306e60 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new baad39b4c1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new b1a51b4308 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 0d8232bce4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new b10ba5adf7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 7eeb29518b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 6720866b07 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 3a5eb6d1be 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 7e86209542 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 5580f59d25 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3190c4c5ce 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new be1c75e9fa 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 55d6ffd7e1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 359b377799 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new db317c6279 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new c28c30f52c 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new ebc07ab780 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ef84f80249 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new c36da28e13 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 778bc20882 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new efb708d038 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 480f05a7d8 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new b68df41533 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 110bd75530 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 48749cc1a7 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new eb6a9c2532 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 8148a52b11 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 1442f65422 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 866b8c02f4 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 26b2b14ed0 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new c057f12cf4 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 60aefc40d1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new f09b7915c3 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new ba18121b18 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new c81bd5f8c0 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5bdfe744a1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 3b066be918 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new c96b2bac24 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8f775ad77e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 9e2ad3a3df 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 793f095f79 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 59e23ea60a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 59c0025d9b 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new c15f2888e3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new fb6bfd076b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 1e9c64d363 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...]
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 (ae99fcddb9) \ 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 1820 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31220 -> 31224 bytes 04-build_abe-stage1/console.log.xz | Bin 72856 -> 73320 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 244996 -> 244952 bytes 08-build_abe-stage2/console.log.xz | Bin 204192 -> 204616 bytes 09-build_abe-gdb/console.log.xz | Bin 38676 -> 38484 bytes 10-build_abe-qemu/console.log.xz | Bin 32276 -> 31972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2640 -> 3148 bytes 13-check_regression/console.log.xz | Bin 6772 -> 7004 bytes 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 47 +- 13-check_regression/results.compare | 18 +- 13-check_regression/results.compare2 | 101 +- 13-check_regression/results.regressions | 18 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 18 +- sumfiles/g++.log.xz | Bin 3401500 -> 3388792 bytes sumfiles/g++.sum | 50 +- sumfiles/gcc.log.xz | Bin 3021316 -> 3019948 bytes sumfiles/gcc.sum | 3415 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036708 -> 1032816 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214976 -> 215264 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2656 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427600 -> 429332 bytes sumfiles/libstdc++.sum | 46 +- 42 files changed, 1951 insertions(+), 1947 deletions(-)