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 56ec3720e4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards b61b795bd7 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 436f015c9a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards b451c4abf1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 34e606fe77 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards b04249e50d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards f14ee6d763 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 96ea83a371 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards e470c38922 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards cd612072a4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards b9bd55868b 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 3fce8aa132 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards e3dd248ec6 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards af721585f4 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 00f184534a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 8c5b390524 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 09fed1f1d8 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 8e7a7044c0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards eed2681e3e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 52369bc543 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a357f0fd56 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 689b1d6bc2 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards aac5c6b408 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 2daa74f288 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 0dc4342471 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards ecdf2c897a 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b4a50ea5cb 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3900764d6c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards b93d18f998 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards c83af5f892 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards c1cdc558b7 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 56913a3d22 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 66b852c681 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 76f904ab3e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards fa617cec81 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards e16e544dae 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 6c0bda2e85 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 636406ff5e 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards decb48f082 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 7cbec3d99c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 83c67c96ae 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards f24518bc53 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 191fdd6ef3 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 32f7395443 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 71101a2324 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 09d8baf45f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 7ae34025a0 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards c1c5f1ba87 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 57de817178 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards c499127f9b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 08f0c4818d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards d677f12be1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 45f8b2e42e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards ef20352fe9 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 47dbe84566 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 88d12389f4 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards d306f0a9ab 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards dcaba2f1e4 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 05bbc832c7 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 05df858dba 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 87b96457e0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2181907315 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 5a47e26465 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 635c6dfdd9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards c62ea046b8 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 5ee00f93ee 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards a2b0b98918 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 5e98992dfd 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 961f3de226 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 9554d86d68 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 5aa78d1ba9 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 3861882bfb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards d33067b47c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards e83d8731e2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 3ce4484462 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards d5071f4bd5 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 3a14eb9925 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 2809ece7ed 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 3326749a1c 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards f3803dfdaa 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 94e48a397b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards eb7fbf2391 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 5c5e934b6f 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards eccedf04dc 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 5b7b4c65b7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 2b2c531ac3 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 91e4b3e185 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 44d50bd1ad 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 1aca8b7ce7 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 4b23e97769 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 34a7542dc7 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 62ef3cad45 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 1f999a63cd 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 3a82a10b58 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards a73453d0c2 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 2046574e3a 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 0c00e903e8 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 6fe5916f4f 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards bd5b7003c0 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards c8d10d95e9 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards ab97e1c231 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new a024baab51 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 406526da57 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 614b75f389 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 2fc8db5954 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 1809dac5bb 218: onsuccess: #2461: 1: Success after linux: 916 commits new a0429b37c6 219: onsuccess: #2463: 1: Success after binutils: 3 commits new ff64439744 220: onsuccess: #2465: 1: Success after linux: 572 commits new e932113f07 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 0ec60de0e5 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 62dea37701 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 2aae5b610d 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 0df7e628c2 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 13ad295e2d 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 0dbc5c250b 227: onsuccess: #2474: 1: Success after gcc: 2 commits new f67422b099 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 4ce7712d85 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new b802040604 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new e525c6b6ac 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 6cd6c60a0f 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 13bfe10576 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 192d102d66 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new c671bd367e 235: onsuccess: #2483: 1: Success after linux: 108 commits new 76634c1324 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 02c6e94317 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 13206af14b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new f262193e5e 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 12a3b0391a 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 02e09bcab2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new ee64baad20 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 4aefbdeb0e 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new c26e12e014 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new c3c9443bea 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 6dd58b91b2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 7406fadc70 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 3f4decbe3d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 6ff5c3a25b 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new c6d4dd39a5 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new b850251972 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new ec90ce3a81 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2bc5a0e980 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new f6bc5c575b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 9b07cee383 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 6a9bbdc824 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new e0f699b1ff 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 3082b16268 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 3b53aabc1d 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 9161d8baa4 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 924eb444c0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 8e79c559fc 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 3aed5968d0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 96d718747a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 000a1a2448 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 608151421a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 2aea652389 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 17ff593cc9 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new a8ca6efb8e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new e400a05145 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 15ba860b3b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new fee017eb97 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 00273d49f8 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 8e1dd1b322 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 4b9843b319 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 02b5b07ca3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 780bd80d8b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a47659266b 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 2a6396ab6d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 9c1b68a091 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 11b6d212e3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 16989b9446 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new b0759e1855 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 6aa1108e4f 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new cb8ed1df6a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new e0a9e2308b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 075d744502 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new ec7f50ba4d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 062a1a671c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new afeefc3fe9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d7bce65bc1 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new dbf45dfb4c 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 19b38e28f5 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ff28a079d0 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new ade3625019 295: onsuccess: #2545: 1: Success after linux: 10 commits new 8ecc891835 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new da99938302 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new df6a062a96 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new f25c6f1b7d 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new a6422159cf 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 5c24a3d44f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 4b941110b5 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 9f657e72ee 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1efe1eb684 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new e37061738e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new b113fe7ad4 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new c2bf1296ca 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 35ae70cdda 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 6516358ce5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 45d4b04f76 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 97c65c26c1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new bf92c258ab 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 4c3aeba352 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 2a5d4ac103 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 017d705895 315: onsuccess: #2565: 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 (56ec3720e4) \ 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32612 -> 32240 bytes 04-build_abe-stage1/console.log.xz | Bin 74448 -> 73164 bytes 06-build_abe-linux/console.log.xz | Bin 8964 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 247424 -> 244176 bytes 08-build_abe-stage2/console.log.xz | Bin 208432 -> 204292 bytes 09-build_abe-gdb/console.log.xz | Bin 39992 -> 39648 bytes 10-build_abe-qemu/console.log.xz | Bin 31668 -> 31540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2800 bytes 13-check_regression/console.log.xz | Bin 6420 -> 7448 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 37 +- 13-check_regression/mail-body.txt | 124 +- 13-check_regression/results.compare | 59 +- 13-check_regression/results.compare2 | 101 +- 13-check_regression/results.regressions | 59 +- 14-update_baseline/console.log | 70 +- 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 | 126 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 59 +- sumfiles/g++.log.xz | Bin 3414792 -> 3410480 bytes sumfiles/g++.sum | 21 +- sumfiles/gcc.log.xz | Bin 3035684 -> 3040424 bytes sumfiles/gcc.sum | 4534 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036108 -> 1037072 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214676 -> 214784 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428748 -> 436840 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2719 insertions(+), 2546 deletions(-)