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 74e77aa1ca 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 33dbba01d4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 3e34c41811 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1eae9952fb 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards c62c7b926a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 68344c0539 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 6e27d7ef0a 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards fa7de01566 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e722dd62fb 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f66e28a2a3 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 492f53e6a4 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 6a742c2d93 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 4f6084b6fa 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 154eb34dac 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 9918df161f 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 4c0532d71e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 3efcebccc4 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards a62c5de151 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards c1dd904f9d 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 4a7cbd3539 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 52f5e3377b 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards e3343a7af7 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 1052eb6cd1 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards eb906c94e1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 222c80a739 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 254b438ea2 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 091ce04d45 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 5bbce64293 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards aa9ca78cfe 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 97111e242d 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 8c48656403 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 61c701b79c 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 702e50d9b4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards ce2099d590 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 2c81059154 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 4ea2d2488e 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards c5ed1720bd 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards bb34544af3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards cc0ef6fc03 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 986b9bf6e0 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 7d88d0d3ef 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 46ba01eaed 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards e8237df4f2 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 5ea5acfd47 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 9e7c0902ee 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 30cfb6bb43 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards b65741d7f1 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards a0bba90e18 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 862756be92 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 353aebd491 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 8ed2b741a0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 644fbb2ef6 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ae7f850ee 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards cc3a517278 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards a4e80816d3 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards c8baff6b0a 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 5c74cbcaa9 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 3a7779cc7f 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 337bc9545f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 80d4579e75 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 145dcacb49 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards c057c10745 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 38985fa017 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards ac0446a0c0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 8deaf4d881 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 550d286a5f 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d52168dd3d 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 8fd393d6d9 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards b30cca4517 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 52d0b79b6a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards d52f1c56d9 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards d9a7ea07df 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6a008906bc 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 430ffcafed 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 8b2d610e11 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 5b8213873a 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards b2b82639ac 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards c11ed3f1c6 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 5b389a4952 235: onsuccess: #2483: 1: Success after linux: 108 commits discards d8b2991ded 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 479439e9b7 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards aedbb00c37 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 991f0c4d41 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards db992ad17e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 7b5fcde6be 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 0cc669bdf7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 7c635060c5 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards eb5749a9c1 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards ea1ac10ee6 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 2f2843ff8a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 8c43ea2e65 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 1b9a6d7d95 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards f270adf005 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards c44d8fab0a 220: onsuccess: #2465: 1: Success after linux: 572 commits discards c1f77d7d1d 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards c501c3804e 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 145de196bc 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 490e7afc9e 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 287640d3a3 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards d519311b00 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 53c9e3da0c 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new a5a32b0f58 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new ab97e1c231 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new c8d10d95e9 215: onsuccess: #2455: 1: Success after binutils: 3 commits new bd5b7003c0 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 6fe5916f4f 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 0c00e903e8 218: onsuccess: #2461: 1: Success after linux: 916 commits new 2046574e3a 219: onsuccess: #2463: 1: Success after binutils: 3 commits new a73453d0c2 220: onsuccess: #2465: 1: Success after linux: 572 commits new 3a82a10b58 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 1f999a63cd 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 62ef3cad45 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 34a7542dc7 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 4b23e97769 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 1aca8b7ce7 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 44d50bd1ad 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 91e4b3e185 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 2b2c531ac3 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 5b7b4c65b7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new eccedf04dc 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 5c5e934b6f 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new eb7fbf2391 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 94e48a397b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new f3803dfdaa 235: onsuccess: #2483: 1: Success after linux: 108 commits new 3326749a1c 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 2809ece7ed 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 3a14eb9925 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new d5071f4bd5 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 3ce4484462 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new e83d8731e2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new d33067b47c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 3861882bfb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 5aa78d1ba9 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 9554d86d68 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 961f3de226 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 5e98992dfd 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new a2b0b98918 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 5ee00f93ee 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new c62ea046b8 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 635c6dfdd9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 5a47e26465 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2181907315 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 87b96457e0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 05df858dba 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 05bbc832c7 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new dcaba2f1e4 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new d306f0a9ab 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 88d12389f4 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 47dbe84566 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new ef20352fe9 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 45f8b2e42e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new d677f12be1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 08f0c4818d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new c499127f9b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 57de817178 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new c1c5f1ba87 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 7ae34025a0 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 09d8baf45f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 71101a2324 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 32f7395443 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 191fdd6ef3 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new f24518bc53 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 83c67c96ae 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 7cbec3d99c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new decb48f082 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 636406ff5e 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 6c0bda2e85 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new e16e544dae 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new fa617cec81 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 76f904ab3e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 66b852c681 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 56913a3d22 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new c1cdc558b7 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new c83af5f892 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new b93d18f998 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3900764d6c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new b4a50ea5cb 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new ecdf2c897a 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 0dc4342471 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 2daa74f288 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new aac5c6b408 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 689b1d6bc2 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a357f0fd56 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 52369bc543 295: onsuccess: #2545: 1: Success after linux: 10 commits new eed2681e3e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8e7a7044c0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 09fed1f1d8 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 8c5b390524 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 00f184534a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new af721585f4 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new e3dd248ec6 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 3fce8aa132 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new b9bd55868b 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new cd612072a4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new e470c38922 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 96ea83a371 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new f14ee6d763 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b04249e50d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 34e606fe77 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new b451c4abf1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 436f015c9a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new b61b795bd7 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 56ec3720e4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits
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 (74e77aa1ca) \ 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32424 -> 32612 bytes 04-build_abe-stage1/console.log.xz | Bin 73636 -> 74448 bytes 06-build_abe-linux/console.log.xz | Bin 8884 -> 8964 bytes 07-build_abe-glibc/console.log.xz | Bin 245252 -> 247424 bytes 08-build_abe-stage2/console.log.xz | Bin 205136 -> 208432 bytes 09-build_abe-gdb/console.log.xz | Bin 39820 -> 39992 bytes 10-build_abe-qemu/console.log.xz | Bin 31880 -> 31668 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 2820 bytes 13-check_regression/console.log.xz | Bin 6536 -> 6420 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 65 +- 13-check_regression/results.compare2 | 108 +- 13-check_regression/results.regressions | 65 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 65 +- sumfiles/g++.log.xz | Bin 3406972 -> 3414792 bytes sumfiles/g++.sum | 47 +- sumfiles/gcc.log.xz | Bin 3042936 -> 3035684 bytes sumfiles/gcc.sum | 5080 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039828 -> 1036108 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214584 -> 214676 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435280 -> 428748 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2833 insertions(+), 2993 deletions(-)