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 6480f6f7ea 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 8a85f42333 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 2b1048f183 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards b7e3d95500 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards fe272ed3ba 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards b312ff86a9 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 1dfb4d85a2 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 0a6bd18f81 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 322cc55965 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards af25d4b2d1 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards df7f450982 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards f9816aa6fe 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 24217e70ff 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards cede83bb9d 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards b6bcdbfa44 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 79ad1a4d3d 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 617082a47b 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards fb0cef8e47 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards ef5865bb9a 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards a0e349c97c 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards e555cb6076 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 6f396db758 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 91173879a1 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 3a8ff07af1 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 6d129011e0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards a2ad78f782 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 555692f501 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards a709e0441e 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 053cb3063b 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards a975cbef2c 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards fdf9bb32b5 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards a2f84df2f7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 2cc72a0f11 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6c63f5bbe1 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 343566da2e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 1aef093e9c 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards adcb6f2f40 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 4835704c31 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards f5174a26ea 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 1111c250e7 235: onsuccess: #2483: 1: Success after linux: 108 commits discards c4ebd6a01e 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 9cf587a8d7 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 13e88657ae 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 5e13fbbc8c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 1a02252430 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards a4e7683a26 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 45f2296d4f 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 456cd42985 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 18d37f4917 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 8cda5304b3 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards c32c7c57ce 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards da5838c974 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 5b6c8da159 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards b3a12f27a0 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 5146d9e923 220: onsuccess: #2465: 1: Success after linux: 572 commits discards cf1d17ec7a 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards d5aa20f79d 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 3e1c3b469b 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 278a002a09 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 751c8c2993 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 56bd5b1b1b 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 0bcc82b5f3 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 834efd5110 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 95b533f753 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 4a9b8ec3ac 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards e7297e4679 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 11eefd1ae5 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 0f28ab9811 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards eab95a0bb0 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards b6e7715f08 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 5e8b1b2f3a 204: onsuccess: #2435: 1: Success after linux: 3 commits discards f9f0e3f0e8 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards d99c51f2c0 202: onsuccess: #2431: 1: Success after linux: 944 commits discards b82c630e7a 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 9b5e2798b5 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 964c4f04f7 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 4347026cf3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 881df30c2a 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 1b6db37207 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 1e4565a477 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 7f7d1f3886 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 50204319ba 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 1d88cf29c3 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 6302a2ab45 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards ee610107cf 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 881eb78ea5 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards a5786b9684 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards c2ef0bca7d 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 6134a29d04 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 8488054958 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 1337408d24 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards b67221f35a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards b7a053a1d9 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards ae70d4219f 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards ff5407870c 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 38907f80f4 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards b8bb5b1ea3 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards ef2f67dc7f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 9f570962e0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 17daa9df54 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 0ce590557d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 037f912ada 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 0707d269b3 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new d1335d71a0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 8fc36d9650 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2395483958 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 7dbdbb374c 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new c2a24c270a 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 3f58a42775 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 9cc5906dd2 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 441c6ffbcb 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new aaa4dd1420 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 3fd81b365f 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 910c0fb23c 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new ba13e3cce6 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 6325034a05 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new d750ed7b7f 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new b41d64594a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 236803ab5e 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new e030c26b13 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 406db77431 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 87e5c21fb0 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new a62193174f 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 2089967683 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new ada2a2fa19 197: onsuccess: #2348: 1: Success after linux: 190 commits new c8591346c7 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 25fda31fb6 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new f73b3b1152 200: onsuccess: #2427: 1: Success after binutils: 274 commits new e82a775dd5 201: onsuccess: #2430: 1: Success after glibc: 26 commits new cd16c17509 202: onsuccess: #2431: 1: Success after linux: 944 commits new 406f207740 203: onsuccess: #2433: 1: Success after binutils: 27 commits new f0389a27ee 204: onsuccess: #2435: 1: Success after linux: 3 commits new e35a39aa04 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new ee44d237b3 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 00c5758439 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 9c0a54322d 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 7685faac11 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 92833bd095 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new dd07f91d3f 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 86edaa3d7f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 6cd1c533c9 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 75e840d4c9 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 825d607224 215: onsuccess: #2455: 1: Success after binutils: 3 commits new f908ab8750 216: onsuccess: #2457: 1: Success after linux: 1736 commits new cda0bc4c9d 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 291f0ef17c 218: onsuccess: #2461: 1: Success after linux: 916 commits new d4d0a27879 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 2d044965a9 220: onsuccess: #2465: 1: Success after linux: 572 commits new 7115343951 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 9e39186943 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 263e1dac00 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new b045d39572 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new a510f07b54 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new e2b2c15cd6 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 87ad096c87 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 9d501c743e 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 54191c860f 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new ea1fade389 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 130ab2f1f2 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 348c14fa87 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 706c2a0ea3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 7dc308a0cc 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new d5aa188000 235: onsuccess: #2483: 1: Success after linux: 108 commits new 44f49e825b 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 82fafdf4c5 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 87adbdeab4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 12767a3070 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new cd85b7e6e6 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new a4fb23de91 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new e5d33ffb09 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 18893980d9 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 0c18046492 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new ec7c5ef760 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new fc2adcf8e9 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 8e6c2f5a0b 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new f29e6e6b39 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 874fe4507a 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 96504a3c44 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 4a20cef8c7 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new f20c2d5bd5 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 9c0824222c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new b1d7eb4511 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 0f4d60046d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 7e790a72ab 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new b884be82a8 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 35772caf52 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new ef302514a6 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new ef82fb20b6 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new c231b86011 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 37e997af5b 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a83ee1e325 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 44fecc566f 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 9459160877 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 61eb9b2768 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new c4d09ab463 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 6aa43c0a88 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new a838870107 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new d7fbf1f138 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 3cc01721e0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 8b1b144b4e 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new f5ff5bba5d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 58bd9f21c7 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 359c6146dc 275: onsuccess: #2523: 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 (6480f6f7ea) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31952 -> 32404 bytes 04-build_abe-stage1/console.log.xz | Bin 74020 -> 73912 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 245684 -> 247208 bytes 08-build_abe-stage2/console.log.xz | Bin 205432 -> 208096 bytes 09-build_abe-gdb/console.log.xz | Bin 39420 -> 39876 bytes 10-build_abe-qemu/console.log.xz | Bin 31408 -> 32468 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3936 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3508 -> 2724 bytes 13-check_regression/console.log.xz | Bin 5444 -> 5620 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 30 + 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 31 +- 13-check_regression/results.regressions | 30 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 30 + sumfiles/g++.log.xz | Bin 3417436 -> 3424504 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3035060 -> 3039004 bytes sumfiles/gcc.sum | 4418 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036884 -> 1041908 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214748 -> 214680 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429100 -> 438552 bytes sumfiles/libstdc++.sum | 12 +- 40 files changed, 2458 insertions(+), 2307 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions