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 73d59edcd6 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 1101ce9904 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 520c86db6e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 1c3d7a8381 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 076ea2d195 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards ecb799fa64 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 9c2e227193 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 371a6613e8 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 873bcf9360 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 4d5d78b4b7 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards e58d159300 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 7d012b155a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 6de113cd0b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 6739b673fa 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 81138a6d26 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards d64f407a19 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 7622376188 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 26ac3f7188 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards d57378817e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards dd909e7488 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards fe662f82ee 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 784d6e2a9c 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 422dced050 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards cf2f9d85f2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards c7f7b1acc2 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 256e5e681f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 8b466f58f5 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards f75933d2e9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a3cd2587cb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 17d6019d99 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d9228fd456 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards e514c9a0ea 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards c52f73715c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 37694fad9c 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards d4df59df55 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards e21878af63 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards bfaeb4ecc6 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards f299c19117 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards ab6a51e051 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 16a24eb9a6 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards c1ee0a92ce 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 74ae4c49e2 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 79b773dabc 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards e7f5b21624 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 4d0d722313 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 3cd9a001d0 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards c9610334f9 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards c4b05b2374 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards b4ca569580 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards ff2f681e06 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 0e4f8f02c1 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 4a5131dc12 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 316b94016b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards a54261ef5e 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 1601ebf9da 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 67c23cbfcc 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards acc762c0c3 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 54d97c952e 235: onsuccess: #2483: 1: Success after linux: 108 commits discards c1e59d2d75 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards c9553dc524 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 7972415f67 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards e7d7de3fc8 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 64be448da1 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 5c66369e66 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 85e2f0eff3 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards d03b084633 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards e78d05745d 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 177cd99e72 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 4b1a176bc9 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 45e65dc6d5 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards feb0097b47 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 02fef3eac6 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 041a8069a8 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 4c63669704 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 4eead1ca7d 218: onsuccess: #2461: 1: Success after linux: 916 commits discards fb6c51ae60 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards c888bc302b 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 6e840b1d98 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 29532f4edc 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 509a43e5eb 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 37b153404e 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards c80b152ec1 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 76e5dd6fe4 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 39a558dd33 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards e4d551ab6e 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 4e52e63248 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards bd57c428ae 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 57981c11d9 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 25716abcc3 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 7dc2294257 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 67c978fd76 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 0213010688 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 0a5246bddf 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 51326fe916 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 82f97c442c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards b66b198a64 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 542c883e16 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 642049d331 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 4edd9b3505 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 4e57fc74e6 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 3eb3999a1e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new cdcd5f5815 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new a51100c780 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 8fe506075a 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 52b41d5d06 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 4d327698a9 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 6bd9c96d82 197: onsuccess: #2348: 1: Success after linux: 190 commits new 19638492c3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new cb84ccac87 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 0399a05637 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 26bce951bb 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 50064bb763 202: onsuccess: #2431: 1: Success after linux: 944 commits new 405a0d1b37 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 37398713a8 204: onsuccess: #2435: 1: Success after linux: 3 commits new 5b60def5e8 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 5d44cb4752 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new d9ea1d56f2 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 8cbabe6baa 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new d468748091 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new cc4cf04798 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 252489f23d 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 525bde2942 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 3b3fad4e1f 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 025147b057 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 357fa736c8 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 2bd1b4ab3d 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 4376a17c0e 217: onsuccess: #2459: 1: Success after binutils: 3 commits new a9fe727a4b 218: onsuccess: #2461: 1: Success after linux: 916 commits new 7012c92197 219: onsuccess: #2463: 1: Success after binutils: 3 commits new b3b57a6703 220: onsuccess: #2465: 1: Success after linux: 572 commits new f24e8f0eef 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 65d92656f1 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new e6caad3b64 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new ac43cbf7e5 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 57b70671b5 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new b9c595aab9 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 52596ba761 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 3e0a3d8d90 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 23feafb11c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new e36192cfae 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 5c4f25a47b 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new c1a5b7f68e 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 21c1ee27ca 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 289db1fbea 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 583e692f1d 235: onsuccess: #2483: 1: Success after linux: 108 commits new 065127ceef 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 315e3b8f81 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new db308e3f38 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 88a35893f1 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 2cfb7714a2 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 8777a3b616 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 066a0607eb 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 1b8cc855aa 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 5f68589f5e 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 7a6bc31863 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 038b5b4637 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 48fa9279ae 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 3751aacc27 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new d04799f90b 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 7dc3c25ad3 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 0507b7a669 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 5c120a770a 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 08680caad9 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 8a61609fb9 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 97274c88c8 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 580bc3a30b 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 158bc3d904 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 88362b6912 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new eb8e0b55a5 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 218e7bebc6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 9358e8e5b0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new db1ec88764 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 33a400fb54 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new af8774aebd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new cb47e39fb4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 0792de1b20 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 5c891912b2 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new f151be2909 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 6d487dfe5e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 6a085f8815 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 94876688e9 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new faa8afdd22 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 7d0db7a6a5 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 6208cd2966 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new df8a14532a 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 63b5ae71cf 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 8e38f98b5c 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new e32ec8b8d4 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new cd7adf0923 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 37f3411f02 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new e9265cb180 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 2a8aaa205e 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 571b204983 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 4bc493a332 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 988e10fbe3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 55306e4545 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new fec3e123a3 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 20594681ba 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 4665963108 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 2ea86b5004 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new fe07e383af 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new ba0f186449 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d6a38b1095 293: onsuccess: #2542: 1: Success after gcc: 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 (73d59edcd6) \ 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 1948 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32096 -> 32152 bytes 04-build_abe-stage1/console.log.xz | Bin 73828 -> 73492 bytes 06-build_abe-linux/console.log.xz | Bin 8512 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 245212 -> 245536 bytes 08-build_abe-stage2/console.log.xz | Bin 205224 -> 204788 bytes 09-build_abe-gdb/console.log.xz | Bin 39684 -> 39564 bytes 10-build_abe-qemu/console.log.xz | Bin 31596 -> 32044 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3184 -> 2632 bytes 13-check_regression/console.log.xz | Bin 5472 -> 5312 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 35 +- 13-check_regression/results.compare | 15 - 13-check_regression/results.compare2 | 27 +- 13-check_regression/results.regressions | 15 - 14-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 37 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 15 - sumfiles/g++.log.xz | Bin 3436068 -> 3410192 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 3009160 -> 3033544 bytes sumfiles/gcc.sum | 4898 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036752 -> 1041288 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214684 -> 214724 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425784 -> 428244 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 2523 insertions(+), 2623 deletions(-)