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 36cfa1b00b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards a7e7725213 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards c7a2e2c306 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 15268d6ece 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards a32a0d9365 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 2acb8fd689 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards ce32c8b7b0 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 7cf439d7f6 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ed1ce708e6 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 1253b6bc57 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards ab8fa00b59 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 611646f3fc 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 8db2f7a7e9 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 77b21247bc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards e5299cc6f2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards da59dd0991 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 2a73014c1e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 13435bec89 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f533c5f2f0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 5ba9f92744 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 7d9390e62c 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 16f0f946c3 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards fc259fdf9f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards c5a3d2dc5c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 8f87bdd85d 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards b1f187d706 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards a3a4a6c071 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 7fb43b1662 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 8830fe3752 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 49453f2975 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 76fbe4f699 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 3668bd2b74 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards c4a395e5f5 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards f61c552e1f 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards dea006291f 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 88c70a963f 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3382c1925b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 376484ec99 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 2543534b04 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ba41f23de4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 3e521941c3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards ca6aa61532 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards f3b2fad74b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 036a27714d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 99c8bc18d3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 35d4855c0e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards db16f3a64a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 82c5b36cd5 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 1db3cc12c6 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 13a4d22231 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 301ed1de17 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 449cb4aa55 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e6f2586f57 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 32f708d22f 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards fd36383a4d 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 8f604c4815 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 47de16100a 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 7f679a3dae 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 08c14511fa 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 29dfd2ea9b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards a788b055da 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 211e19e89a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 9674fd3ded 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e644a5293e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards c9814a1980 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards cebb3b0498 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 17dc9059ea 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards e5fb7141ef 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 80e868a7b8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 9beb489306 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 88360f9e9e 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards f957794bab 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards b8411463c8 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards afa8d1a31a 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards d7c464c4d9 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 7835021bc6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 6917b16ec4 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 48a24fe00f 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 97f81884a7 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 628c84e83d 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 82320302a8 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 20f2aa4199 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards b3ada949dd 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards f7289ff30e 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards eee0dab848 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards b0653a8ee4 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards bc0ee45a8d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards f198cf690e 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 4747a23089 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards cd55431752 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 0b57f13626 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 43e85b808f 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 3b850ae116 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 56bef199d8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 549308063d 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 4325e404d5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards b20bb18afb 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards a5689c90c7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 263aecb449 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards f202c37339 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards a4f92177d2 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new d77ed012bc 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 2c75b32b4f 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new ada2edeca2 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 58e7657d36 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 74ba4d86b5 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 93534f8fc8 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 99a5c63e2b 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 34df62ca7a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 17041ca971 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 2f71efe0e4 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 9c010922df 235: onsuccess: #2483: 1: Success after linux: 108 commits new df53648b79 236: onsuccess: #2484: 1: Success after gcc: 2 commits new acc4c4d4c9 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new b467e26eb8 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 3ff2ad9082 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 147b23678f 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 76c733627f 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new c05404ed4c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 67313ed519 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new daa4201a6d 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new e61acff87e 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 3e8890ebc0 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 329555a130 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 811a4bafd3 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 9dc2a6759b 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new b8fe211e40 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 05be1f51a6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 636d662820 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new eabb304bfc 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 815f76bdba 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new bacc443948 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 757ac0b2db 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 4cb00c28d4 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new ba8fe58a07 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new b030420d93 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 7c1fefbf40 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 8aa7ec1dda 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new c181d6743a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a4f7f8b284 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new fa2a5e2ade 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 4b12ae6e3e 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new c40fb63d16 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 8587e09983 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c13201fdef 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 6223768880 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 70cd4e35a7 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 746e6410ab 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new d0f14d37d1 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 14e13290b6 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 21f12d1aa1 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 9a79c49f21 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 66919ca767 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new b36b2d4790 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 0f6d5a8c3e 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 639bfc3216 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 255ec772bd 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 6b9c1a3909 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 512408594f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 05d6d610b8 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new c90303860d 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 63c6bcf842 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 9ad38b92d3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new b09483ba2c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new b2d941a1d5 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 31b1b9e939 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 56a0b1473f 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1bb5060adb 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new f40e5f4cc1 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 212bb9421f 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 9d2b57d6f2 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 489d3af45b 295: onsuccess: #2545: 1: Success after linux: 10 commits new aff777c1a2 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 9b02000b96 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 4ebb9a4dc8 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 94ce3776c4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new e855dd2d1f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 26a399bf03 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new c5eec7fff9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new ddc39aec2c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new a25a59e632 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new eebe4a2b41 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 1a767e3e5c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 0c132d7423 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 20cba61b13 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new d923add8d3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 0d83ee849d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new dc19b5fdfc 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new e4336745a0 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 76bccfef80 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d8513381f7 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 61b4079964 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new ac610c6e2d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 8cdb3cba9d 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 02ad2cf2e9 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 4381964a71 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 9d71294a6d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 0921b11d5b 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new eb00617f2e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 89e13395a7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 69ac58d548 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 8bb8f2c15a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 0e18c6658b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 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 (36cfa1b00b) \ 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 1836 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32320 -> 32384 bytes 04-build_abe-stage1/console.log.xz | Bin 73748 -> 73184 bytes 06-build_abe-linux/console.log.xz | Bin 9272 -> 9248 bytes 07-build_abe-glibc/console.log.xz | Bin 246560 -> 244684 bytes 08-build_abe-stage2/console.log.xz | Bin 207904 -> 204188 bytes 09-build_abe-gdb/console.log.xz | Bin 40200 -> 39776 bytes 10-build_abe-qemu/console.log.xz | Bin 31988 -> 31956 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2836 -> 2756 bytes 13-check_regression/console.log.xz | Bin 7516 -> 6068 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 31 +- 13-check_regression/mail-body.txt | 98 +- 13-check_regression/results.compare | 52 +- 13-check_regression/results.compare2 | 138 +- 13-check_regression/results.regressions | 52 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 100 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 52 +- sumfiles/g++.log.xz | Bin 3424336 -> 3416272 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3029484 -> 3034088 bytes sumfiles/gcc.sum | 4454 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041352 -> 1039488 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214584 -> 214900 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436184 -> 433464 bytes sumfiles/libstdc++.sum | 20 +- 41 files changed, 2572 insertions(+), 2580 deletions(-)