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 4f760b11ad 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 654fa6abf6 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 3709ac4aa4 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards c3b8df3568 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 46350a5fc3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 4c7f98d574 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards ad6cc2f364 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 7ac304eec1 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 0ba05d6b39 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 446db3eb8b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 2d2e34fcb5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards bd32020bdb 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 4dd5a4ad99 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 052aa9b76c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards f1cbc62040 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 4831930d9d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards c09413968a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a5ec3ab48b 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 26f038d4f9 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 9a896e4eca 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 0efe4c2196 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards d0fff35600 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 18b7599c77 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 654d80f4d6 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 130ce1568b 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 36f9fc50dd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 9f0e0bbb12 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 1cd49413fc 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards fd47c5e714 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards acb357ce00 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 08c18385c7 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 035365a5d4 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards dd903b655c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 497ea19e10 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards e304712ffe 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 120d722d86 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 33b10037fe 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 97eb77ff86 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 1860dc9cd0 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 81423da099 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 692ccbc5f2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 0fad7550be 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 634283134d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 438564319f 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 380338a89b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards ba0a7a2e26 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards b59df6e317 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 04aba8765e 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 10ff0ae576 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards bacebdd016 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 34dea25521 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 0e6876ae59 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 3df53941c9 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 0fc12a2ed6 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 72e4247566 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 7a1a4da897 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards faa1dd7c3a 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ded2f72191 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 0ca525c407 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 9906a1e21b 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 51ec43a897 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards f90ebcb3ea 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 2558c30315 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards f011d87950 218: onsuccess: #2461: 1: Success after linux: 916 commits discards c7187092bc 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 147e9f1665 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards a7fe1a2d18 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards ae5be77fc9 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 25bcc28a5d 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 4dfbd6346f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 56c8334e52 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards acebecbeb8 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 8c4a877ca7 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards db4e8c0bf2 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 6bb499538e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 6df4a49c7d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 172a8d89a9 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards f722ae14be 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 55b3081afe 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 495631de9b 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 9bc4b7239f 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards ff652b717a 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 2a55bbaedf 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 2539d25c6b 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards cb889851b4 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 11be4d5c47 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 7624338d4b 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 45f75aa949 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards e143bf0961 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 97dd0cc542 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 92e6da0219 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0e961e77c4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 05c1ef0008 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards cf68837c80 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 1c5bdca66f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 1e94ead259 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards b8e1258e1e 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 04ff8c88e7 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards f322dd39f8 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards ac5b81239e 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 32ab0ad0a4 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 585077afc8 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new eb60481bb5 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 18195f3a3c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 32db47433f 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new df9d3728b0 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 33c198f7a5 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new c2bbdb4b15 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 31c44105e0 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 7073aa786c 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 1f88a7aa6f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new adcdf0ceb3 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 22b82f99ff 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 9ae07e7f4d 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new de277c4c99 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 79b5c4d2ed 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new b23eea0fbb 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 0cef90c33d 197: onsuccess: #2348: 1: Success after linux: 190 commits new 7a7ae68eb0 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new e03d124421 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 2a46dd0679 200: onsuccess: #2427: 1: Success after binutils: 274 commits new ce5f23519d 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 7376be3526 202: onsuccess: #2431: 1: Success after linux: 944 commits new 4adbe5557c 203: onsuccess: #2433: 1: Success after binutils: 27 commits new df02e002eb 204: onsuccess: #2435: 1: Success after linux: 3 commits new afefc7f374 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 6a560db398 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 33a2dc3dd5 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new b1699f97d0 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new e7fc83ae69 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new c1bfb80af2 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 20bb392c55 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new abd756c625 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new f31ab0717c 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 4e9b5f5c79 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 8fff2ac65b 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 06f60b2485 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 2e846b2814 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 2700dd0dda 218: onsuccess: #2461: 1: Success after linux: 916 commits new bf1a170cd2 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 20ae1b1ffb 220: onsuccess: #2465: 1: Success after linux: 572 commits new 6f2b6ed4a2 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 9887e7ca45 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 1dcee312fc 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new de3f4a20fe 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 4c5d2e6c04 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 699929e58a 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 3cf8a12bb2 227: onsuccess: #2474: 1: Success after gcc: 2 commits new b5dc902384 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 9ee44f1875 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 5bcc3b2819 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 39cb1347f1 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new bd259f16e9 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new f09edfe937 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new f052b65a39 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 998765dc21 235: onsuccess: #2483: 1: Success after linux: 108 commits new 9782e67267 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 64bc2251ca 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new e47bcb6d1e 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 439c9c7471 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 8ee1d97236 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new e36d7c0e00 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 5fe3c9b64a 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c87fbaeb09 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 54a97bfd8f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new ad8d78d114 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 2b5a0808f2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 47f8717a9f 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 2857f41795 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new e3e17f5850 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 32848e3419 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 62e49c9ca7 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 880d0c8416 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 7f54a06393 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 4124188969 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 4358fc80c5 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new e5770c1fd2 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new a3591e2900 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new c4b795a5f3 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new e607c8aa0d 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new dafeb37510 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 9268ef9277 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 6c2f85720d 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 9eb39b1b64 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 2a39e48cf8 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new a4468fa6de 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new ade58c012f 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 1ec230a3d9 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new d8eca9c4c5 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new c2b277f8b2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 880d0ff3d5 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 2cae9d5b1b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new f868e5888d 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 4b934e139d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 8f0472307b 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 3cc79eed93 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 393831b290 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 11bf4db934 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new d1bf06c209 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 2ac1b154fa 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 11bac6994a 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new d0cd868241 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 9db91785f0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 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 (4f760b11ad) \ 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 1804 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32584 -> 32024 bytes 04-build_abe-stage1/console.log.xz | Bin 73780 -> 73004 bytes 06-build_abe-linux/console.log.xz | Bin 9040 -> 9044 bytes 07-build_abe-glibc/console.log.xz | Bin 245800 -> 245260 bytes 08-build_abe-stage2/console.log.xz | Bin 205232 -> 204636 bytes 09-build_abe-gdb/console.log.xz | Bin 39984 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31676 -> 31988 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3140 -> 2628 bytes 13-check_regression/console.log.xz | Bin 6544 -> 6288 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 13 +- 13-check_regression/mail-body.txt | 75 +- 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 49 +- 13-check_regression/results.regressions | 37 +- 14-update_baseline/console.log | 60 +- 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 | 77 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 37 +- sumfiles/g++.log.xz | Bin 3416872 -> 3415752 bytes sumfiles/g++.sum | 45 +- sumfiles/gcc.log.xz | Bin 3038816 -> 3034484 bytes sumfiles/gcc.sum | 4350 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041864 -> 1036600 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214572 -> 214632 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437008 -> 429900 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2453 insertions(+), 2393 deletions(-)