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 e7041e3fac 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 7e8ec0ce2e 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 14697b7575 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards ac61ee13bb 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 96a9a8634d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 797f8038b2 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards df1ca87da6 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 31a547e708 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 44ab2049fc 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 4086af7895 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 7d73917e2a 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 080739fffb 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards e91ad2cb4c 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards e34be44b96 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards ebbea6f4f9 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards f3a6dbe8ac 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 5b23f9465b 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 7b45219ed8 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 1d61eba32a 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards fb912f9571 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards a1fd5a2ee8 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 428861fdd5 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 455d399ad8 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 05cf453007 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 64c9cb604a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 9c2d4e7595 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 81fff2ba86 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards aff1fa4467 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 0be391d598 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards ba02e9bde7 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 2a6bae781b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 6bfae2d210 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 76e6c35925 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards d73b648b8a 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards d108ace559 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 729f7aa73c 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards e9ffdf24eb 235: onsuccess: #2483: 1: Success after linux: 108 commits discards ce2e1c7890 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 8e6896f846 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards c28695d88d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 1244f1bf42 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 2b80d8c6e0 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 8b81313b5c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 2da7141e8d 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 8b8c79be0e 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards c8a5464dc6 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 48090515d5 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 28d15a7108 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards d04ee8a421 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 427d8a2fd2 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards ef27bf1d71 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 58ccc0c932 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 4bb2f8d773 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 7f1645b376 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 2ae21d4c08 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 370cb6060c 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards eafd5a1497 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 3600734c79 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 71b24ba6e9 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 3ecde34203 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 83a47939b0 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 8a76448869 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 7ad0c89bc5 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 3600e10478 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 967578d3a7 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 254ffcb1a5 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 9f676b3bdb 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 446a01d445 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 82e839b4a2 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards e316430014 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 3754461cfa 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards be23ae5924 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 47ef35b82a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards e3968aadf7 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 60be2807b3 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 047c9d6313 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards ce24c36ce0 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards b8df9d96f9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 772354a2d5 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 64f01c65de 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards fe15b324de 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 409eb62ff4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 659d94c8d5 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards c0986e6728 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 776a99db0b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 76ddf31b0a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 672f3ed7f5 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 7e900752a5 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards a47e2ce529 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 2e53be617b 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards d202610ea4 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 0b8dbf89b9 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards b4d3e52515 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 161b82cafb 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards f4817d169d 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards db1a442715 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3e8bfc8c7c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 5f3af37b5c 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 6c36b17be1 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 89398bf558 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 41dd3ea2bc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 426da7964f 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 946b979782 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new da976f9848 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 2958601b10 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 758715aa96 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new bb9a6c089c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new ca53e0fa41 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new a6d6e52d4a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new bd88b898a2 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 4c01bd852b 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 70f4331d1b 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 59e936e51d 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 1c4320aa27 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 21896ddbe5 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 564317914a 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new d6586f330f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 288b127833 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new dd2cc0200e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 51bfa37c0f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 484cfff965 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 1afdb52296 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new a9efee1888 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 58cba5c7fa 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new bd33d8a5eb 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new aa0d84f3bb 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 4ceb700870 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 5c580bbe4b 197: onsuccess: #2348: 1: Success after linux: 190 commits new dc64c77573 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 768f7ef4c9 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new e2ff1a1f25 200: onsuccess: #2427: 1: Success after binutils: 274 commits new a52e949138 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 50302ccd0f 202: onsuccess: #2431: 1: Success after linux: 944 commits new cd518e09c1 203: onsuccess: #2433: 1: Success after binutils: 27 commits new d35c9327b8 204: onsuccess: #2435: 1: Success after linux: 3 commits new 3abeacca35 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 000ac86bb2 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 1c95db7e54 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 13c99e94b1 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 4daea4b301 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 6b74b4de06 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new be1fe08004 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 69e3218d00 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 939e3ea0d3 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 7249b1ca7c 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new c4a7685bb1 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 25a327ff70 216: onsuccess: #2457: 1: Success after linux: 1736 commits new d6e8261aea 217: onsuccess: #2459: 1: Success after binutils: 3 commits new ecc27bf179 218: onsuccess: #2461: 1: Success after linux: 916 commits new c9e4cb3488 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 61021cba6e 220: onsuccess: #2465: 1: Success after linux: 572 commits new 6ac0172127 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 03ddb53241 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new dbb090e4c0 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 70cad84736 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 33a89842f8 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new ff0372dc4c 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 943867dcd3 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 8a8edca952 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 1b8e3f4ee7 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 7518aad7b8 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 84fc47dae0 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new d3e2aa4d3a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new c7ad5bee9f 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new b092efc4b2 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new e17389ae71 235: onsuccess: #2483: 1: Success after linux: 108 commits new c4c31ab052 236: onsuccess: #2484: 1: Success after gcc: 2 commits new daff3f4cc6 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new f2da7354fa 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 71b7f293a3 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new d02c87e156 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 268b44bb0c 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 773ba2c64e 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 6013210a9d 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 296fb27cd1 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 7d0a76cabe 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new a96e844f3d 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new df445d0907 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 5f16a0db4d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 816e530a9c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 0aa493816c 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 4bd6d75824 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 7ba66974be 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 3b887e6994 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 57c526cce0 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 049fd56dc7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 07fb1a17cd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 1bce5b4a81 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 3333bc94bd 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 884406d42f 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 667bbfba25 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 0557050c0f 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 0e13cb81d1 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 644b67a3a4 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new ce6c1ee6fb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new ad93f4abc5 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 39dd7616e4 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new fceadada96 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 3300eab3f4 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 5ec9543d4c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 2f3f454df7 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 7dd78583a8 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 06d12279a0 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...]
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 (e7041e3fac) \ 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31972 -> 32020 bytes 04-build_abe-stage1/console.log.xz | Bin 73136 -> 73532 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 245428 -> 245196 bytes 08-build_abe-stage2/console.log.xz | Bin 204564 -> 205016 bytes 09-build_abe-gdb/console.log.xz | Bin 39260 -> 39400 bytes 10-build_abe-qemu/console.log.xz | Bin 31440 -> 31416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3936 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2652 -> 2760 bytes 13-check_regression/console.log.xz | Bin 6316 -> 5144 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 72 +- 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 30 +- 13-check_regression/results.regressions | 44 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 74 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 44 - sumfiles/g++.log.xz | Bin 3408516 -> 3410700 bytes sumfiles/g++.sum | 6 +- sumfiles/gcc.log.xz | Bin 3033720 -> 3031596 bytes sumfiles/gcc.sum | 4880 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042596 -> 1038988 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214760 -> 214656 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428604 -> 434024 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 2545 insertions(+), 2769 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions