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 30184e5294 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0b75de6eef 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards b4ff9d0265 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards c4089754c3 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 10f75b3ccc 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 185eb4aae7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 57950b3435 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 7ecba8286c 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 70d6e18455 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards c5500cb5b7 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 7aec6f98e7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 7842f88819 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards d86d602b01 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 852c51ee55 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 846852e0b3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards ab6a22f4a4 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 7a5ac7283b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 2fc843abd7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards e97f8f040e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 284796af61 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards decd4758c3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards f24dc67511 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 2e6b76d055 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards ca74fafbae 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards bfbd489015 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 434fafd685 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 574db564e8 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 295bf33a08 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 836f3fe114 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 9782d42e0c 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 392efc97bf 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards c382ddb06b 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards ac03b9ef50 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 7baea607d1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 03dba8a975 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 4e07c22b12 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards fb342c03eb 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 43ec28ab8a 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards cbab43b2d9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards a51754963b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 51339b6f30 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards c2a2b9820d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 00d7514a40 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e84470e0c4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 8309e17294 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 822bd5720b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 7f0a3d12fc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 0776103477 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 6cf925f686 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards f792c7b256 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 3ab4c97558 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards f8ce924775 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 360b6ea4d4 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 9ac132f74c 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards aaed60b10a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ae99b7fa01 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards ef7ce37a34 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 2ef63c127b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards ff76d03c0b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 961556973d 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 4e880107cf 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 6ef25a3460 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 940e82cb10 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards f38e46111e 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 4b11df39f3 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 5a2502b1fb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 39e578d796 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 4889a3fd87 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 69ab9b580d 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 421c5b3cf6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards a38f95644f 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 67f485b086 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards f4bcb952de 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 97ebe94d99 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 1a014e61e2 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards cefcb0dd67 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards aa89419799 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 4c268e9d96 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 656ac5349b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards f26f434ef1 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 71055f702d 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 412de5eef0 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d5536659fe 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards f358957e31 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards bcda594e35 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 80df272c97 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c72c83ab1a 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards ce7a101eb6 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards cde218ee00 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 2bcfa6d325 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards b17c135682 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards efd2730c9f 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards b402c26093 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 261b88cae5 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 9cab6bd1c6 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 718006f7f1 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards de579c2ec8 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 256100420e 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards f4fbdb1a15 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 60db4b8c7e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 8bc661eb86 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new ca8239573a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 26e67beb1c 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 634dadd6f6 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 8ac5daceb5 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 86508b4e75 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 4d09ae9c3c 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 4dbae9a0cf 235: onsuccess: #2483: 1: Success after linux: 108 commits new 479efa1a4f 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 241ba3e1a6 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 5ec123f915 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 8a1488623c 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new d700b17f1b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 6f0f747740 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 4cd75f9e6a 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 58c349a7a3 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 002b0a653f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new ef8622ba03 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 01b835a9d5 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 703a2dd044 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new fdf8b1e703 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 90156bcabe 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new a629a3c71d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new d35fd5a19b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new e1baa682e6 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 08e95d281f 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new a6ddd71b23 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new a274a6569b 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 509a6cf7de 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 5b7edba775 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new c024101b8c 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c6b980ac52 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 26c165e5bf 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new de60366444 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new d59ae51d07 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new d0de722139 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new f71f00f289 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new f17eea228a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new e1c2a5ea7a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 4de63d2c93 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c390c695c3 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 06281f10ae 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 7bcb53a9b2 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 34e326f668 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 7480aa631a 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new ff17b1506c 273: onsuccess: #2521: 1: Success after gcc: 2 commits new f25a4c121d 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 32fc9a31af 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 69e68c467a 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new f39f788c58 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 181cf4adbe 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new b15555e429 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new dbce0243dc 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 750b034ce5 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 37db52cbd8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 099dd0888b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 73fbaf4912 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 3a2f2d59b9 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new ec1365810c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 99791160f8 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 94cafc8719 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 14f443a9a1 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new fa6a6b4a6e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new c471dabfdd 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new aa47cc2066 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 0667cffffd 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 8d56e14efc 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 0c4078762a 295: onsuccess: #2545: 1: Success after linux: 10 commits new e52d0bf147 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new a759fa2100 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new ad8df0dc1f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new fdd2cb3df5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 9052ce9f9f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 42b4ded543 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 2787e87c3d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new d05662d6c2 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 864c14ed06 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 35860a4be6 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 7fe2aa044a 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new c0b51038c1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 93746cb655 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 0e82df301b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 08580462b0 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 045feba4ba 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 3e4f2510e6 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ab954c0582 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 34b758362b 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 6aafc49cee 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 98fd4c2d9e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new a210b8ad87 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 5378bb18d0 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new bc1241e64e 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 530cec5df6 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 0c7416bda5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 429d15ca85 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 04f8735495 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 0228b58b88 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 84f6e2b5d7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new ed3519c389 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 1e82fb72e1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 33d13097cd 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 83146820fe 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new a2416efdce 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...]

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 (30184e5294) \ 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 1772 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31956 -> 32012 bytes 04-build_abe-stage1/console.log.xz | Bin 73412 -> 73000 bytes 06-build_abe-linux/console.log.xz | Bin 9408 -> 9416 bytes 07-build_abe-glibc/console.log.xz | Bin 244944 -> 245240 bytes 08-build_abe-stage2/console.log.xz | Bin 204584 -> 204316 bytes 09-build_abe-gdb/console.log.xz | Bin 39448 -> 39356 bytes 10-build_abe-qemu/console.log.xz | Bin 31984 -> 32520 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3948 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3012 -> 2748 bytes 13-check_regression/console.log.xz | Bin 6436 -> 5576 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 13 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 16 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 16 +- sumfiles/g++.log.xz | Bin 3420112 -> 3413788 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3041224 -> 3032036 bytes sumfiles/gcc.sum | 4938 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1039792 -> 1042324 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214736 -> 214748 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429820 -> 429012 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 2587 insertions(+), 2670 deletions(-)