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 e3f6aa79e1 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 3c2445b6a6 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 68745a2062 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards bc703a8419 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 0fec9e6385 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 5055723747 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 6c7f13f1fe 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 54974a6355 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards df89c4c7db 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 96003f0a66 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 539e2a1b55 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards d4be020b30 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards d65d6dd86e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 51eaee63fa 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 829824b153 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 76f573362c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 22849325b1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards d58d325116 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards ae84a265f9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards ea290d4842 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 08619f0dad 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 97f398f6d9 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards ddff857d34 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 646fce9d42 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 892ca8dd23 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards cafadabb15 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 249e59e3ee 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 115974da15 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 03d9174bc8 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 73a19988f6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 6a7753ed59 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 7cdbaaa16a 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards a0aaed462d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 5c7f5946ee 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 6cf676cd44 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 19a13b5052 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e62b00fa57 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 14939aced7 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 417abf3a95 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 70bde98810 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 94cafedc9b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards d5b09f7844 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 1b89ae3f1c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 9670138d90 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 61c9007d7d 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b21f2630c6 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards d3d908efbc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 20cbe0bb75 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards fb8f3dbf2e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 6e17f5c20b 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 6b791eee99 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 5d5b21cc5b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 6d6060eafd 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 1b5690c6ad 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 4d0025aad4 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 654319781b 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards f8fad941db 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards dce1530b12 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards d434e5ac49 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards b52f5143fb 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 05a77a704d 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 4522a12f58 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 0e61638df5 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards a1c17c7b9d 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 77b7a1aa4c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 0782fa1670 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 414ed57e92 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 6393a90ab2 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 5e9d2a69d0 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards a136240d5e 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 88d37c65bc 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 0b378bad99 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards ca334ef0ff 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 0eb6352290 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards e46b2c6291 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 98cc4fd0a6 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 8a28d1b1b3 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards f30e890171 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 8666c3ab0a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards a531dd2b0c 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 67b7ebdfc1 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards abe82409bf 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards dde718d501 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 835f8163ab 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 025aaecb02 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 8f0246f908 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards f1fb4f28be 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 04d4197695 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 1517b4ec49 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards d1083b5292 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 0793e6b0f3 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 4116582cca 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards c880aeff5b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 0e8f8a99d1 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 1de84a2478 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 1313447eb2 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 595a3c6093 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 596c4ded33 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 9ff00705fa 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 1b74584d0e 218: onsuccess: #2461: 1: Success after linux: 916 commits discards f0c67dc9eb 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 65e2bd2ad7 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 766de876df 218: onsuccess: #2461: 1: Success after linux: 916 commits new 30d3ef79dc 219: onsuccess: #2463: 1: Success after binutils: 3 commits new eaf0c5c683 220: onsuccess: #2465: 1: Success after linux: 572 commits new 359eb85615 221: onsuccess: #2467: 1: Success after binutils: 3 commits new adada62d3b 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 2462803077 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new ee2f5b33be 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new fb0794df88 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 19b3dc2795 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 73fe2b20b5 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 841b7c5572 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 56c680b7fe 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new f05d9367da 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 6bec1e1b0e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 7880cd5e5d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new f5b5635605 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 7ee9e14722 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 5128482de5 235: onsuccess: #2483: 1: Success after linux: 108 commits new 163e80c9aa 236: onsuccess: #2484: 1: Success after gcc: 2 commits new eb4d57e3c2 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 5b1b7bb053 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new c5d3a46c10 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 5b880aa051 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new f4bfc91994 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new e23dbec789 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 82a0bd94ac 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new d81240649a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new a7ab120ea1 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 17044d4e23 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new dee92e82a9 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 06dcd50f5c 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 2418777f6c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 18261da0bf 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 5cbff4b11d 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 281882c045 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 2fe835a4ba 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 915cbdb54b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new b741f98923 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 48c2ad6147 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 68f9b5bf12 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new d136dfb54d 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c065fa83e3 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 8dcb92dbd7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 0198cd97c3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 3c0f2ce79d 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 492095e398 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 2eb364b450 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 77594aadc3 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 335e3e3faa 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 43e5211921 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 3257957ebc 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 149744ca23 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new c38632b436 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new d7ad8a1d9e 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 6c57fcb648 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 8165f83e61 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 3b6e2cceb3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new be32bbc2f0 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new fa7a72d0a6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new afd2c9b6e5 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 0caeda47c2 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 771c3d50a9 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 3c0ad7c9f4 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 15bb63134e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 1039c686a0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 6e7b326a94 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 33f831a4a4 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new dc3fb2ab78 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 476cfbf07b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d7c56cdd81 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 24753cbed6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 951f64b4ae 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 6ad903976a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d4771978ec 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new f80d6b7429 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 80073e4a4e 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 861d201a23 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 5b550a5bcd 295: onsuccess: #2545: 1: Success after linux: 10 commits new 0338c434c0 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 125d98785e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 00d82a2e4d 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 744cd33508 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new aafa0f4f6a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new d158e8df34 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 2e9d20684f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 9e71720586 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 9ea88e469a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a8e1e45d13 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 1ff8daea1c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new bf0af3d6b0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new a50aa760fe 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new a7c11c6ed5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 752911b509 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 809c5e9a07 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new bbf4b68801 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 8c58a92436 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 47647e4ed8 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 8e8b06080c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new c13e19695f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 51c1f81b15 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new af1a875236 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 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 (e3f6aa79e1) \ 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 1796 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32796 -> 32128 bytes 04-build_abe-stage1/console.log.xz | Bin 73844 -> 72984 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 245588 -> 244460 bytes 08-build_abe-stage2/console.log.xz | Bin 205364 -> 204184 bytes 09-build_abe-gdb/console.log.xz | Bin 40092 -> 39684 bytes 10-build_abe-qemu/console.log.xz | Bin 31688 -> 31504 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2628 bytes 13-check_regression/console.log.xz | Bin 7164 -> 6036 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 28 +- 13-check_regression/mail-body.txt | 134 +- 13-check_regression/results.compare | 63 +- 13-check_regression/results.compare2 | 147 +- 13-check_regression/results.regressions | 63 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 63 +- sumfiles/g++.log.xz | Bin 3409120 -> 3407620 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3039344 -> 3033448 bytes sumfiles/gcc.sum | 4860 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042192 -> 1038640 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214848 -> 214780 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427396 -> 431500 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 2832 insertions(+), 2833 deletions(-)