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 f53b8ddb15 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards e50fa69c6a 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d87f8cf4eb 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards e4b9934bb0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 7424101fa6 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 24dea51db5 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 5c9144e83a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 9a54c15f5d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 0cbdd8f242 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards de4b861db0 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 089180930c 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f7904ee271 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards e4504eadd9 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 68c6f3fff2 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards ab832309e5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 5ee3ed1d17 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards ffbd594f0c 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 9a98c3405e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 83093d31ba 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 96424bf31e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a786311f32 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards c0afc884ca 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 380c6825f4 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards df2f0bedda 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 458bee8aa1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 2c24b754d5 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 0d56ff6781 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 9a9f5b4394 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 30b7711532 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 48e6356230 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 242e9ffcca 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 56f4df2111 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards de6bf54a33 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 3e98562169 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 17d1ccd8ec 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 0a56b10063 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 64747e660b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards d4e37ee607 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 7e9d71aa71 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards a180963915 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 47ec4d7f4e 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 19de27adda 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards c60b113f6c 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 80b9794e4f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 4512ddd5e3 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a96fcd2057 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards d7f9cdfdac 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 84d9ac3ad9 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 29efbf726d 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 48731c4664 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 280855bbfb 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 4e5f89deed 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards c751031eae 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards c3c17465f2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards ee4889dd5e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 7fa9989262 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards bafcc231eb 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards b081513368 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 7668fab8db 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 094e48cf8e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards a0f9f0a547 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 7b21e8c0d1 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 157b89f2a8 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards c7b13a3d3a 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 07ab171388 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 9680e510fd 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 28c267a62d 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 547a54daf2 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards c7c6f3f5f7 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 2ec255feb4 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards e71d2efa64 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 14e5253bb1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 1afd7d4387 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards a5af06f24e 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards c2fd3f1c9d 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 587ebbf80a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 12b69eeb66 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d02b9898eb 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 345084e80d 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 8e744d24e0 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 4b7ae7efad 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 11abacdc69 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 1945f13e6f 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 3669d591e1 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 6ef468f55f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards bf6529ce94 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards ceb3354b93 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 60037737cc 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 5a87c1e500 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 6b29dfcb19 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 501ef64768 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 81e0539551 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 8c95818b4b 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards e9ab679f46 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards c0d0aa2a75 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 3a8912eac7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c74dfb36b9 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 2e7cf1946c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 6698e3c78a 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards a163cf4447 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 200bb0041a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 0f30b87d76 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 88daec143e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 13b830cc45 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new cb870631c9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 127cefd6d1 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 30ae7a215f 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new db0b9a4245 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new c38712aeb7 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new c1ef2dc833 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new e479610ebd 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 22e072f833 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new ef8a9f4c96 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 140a740592 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 015ee3360f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new fc29498221 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new a484e064e5 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 0537485319 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 08ad27dbb8 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 17c3fb494c 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 5cfe9e2868 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new ff90939881 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 6fa0f61465 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new a4fb1439ce 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 86d0084a07 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 61b0673e6c 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new a9dea981d4 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 70b77fe9c5 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new c8b9dc4e91 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new d7a118d26f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 65cfff9750 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 25858eb1b8 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new bfd680518b 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 9d751b01d0 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 8b7c82fee3 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new a48fddef6e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2c03874212 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 295f22741b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 87fd651598 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 4665bfdb8e 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 8666e05e00 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 7c6b21cb01 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new b1b0d1c79b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 0941a0ae2f 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 9f504b3cd6 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 6aab94eb6c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 3a319324c9 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new fdd4987c1f 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 3ba493e228 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 38af4e331d 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 994f54d718 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new f60215649f 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new d388e7c3d9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1f20adadd5 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 515725e48c 292: onsuccess: #2541: 1: Success after binutils: 13 commits new b8231a1cd2 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 0bd960e9da 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new ead5b6f03a 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1fcdc06a07 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new a949989213 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 03f9ec0467 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new dd4a1e44ff 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 900fb96af9 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 9cc64889ab 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new aeb2426ba9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 780efc81f4 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 72b918eeae 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 03d4dd90b8 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3c995f405d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new f6d88d51b3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 089d565311 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 20b808b535 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new a361f583cb 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new a7b1cc359e 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5f18e676e2 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 3f535a97df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 87f60b70f0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 8e995ebb61 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 0b915a565c 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new d326b76ea9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new d9fcff59cd 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 66c663f030 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 37955c6600 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 81dd6dff03 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new bf329343a5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 2135747166 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 12b79d166b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 4c2cbbf23d 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 131b83f796 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5cacffb072 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f2df72bd2e 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 7608a1d004 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new e8d0be12e0 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new c7ab8548a7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new e885583d21 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new eb22e09a83 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new b2fe92119e 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 46ca20c662 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new c77ed5ed66 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e837997d44 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new c85150bab9 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 9fc67ae714 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new a78fdc2779 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...]
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 (f53b8ddb15) \ 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 1780 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32288 -> 32468 bytes 04-build_abe-stage1/console.log.xz | Bin 74128 -> 73192 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 8352 bytes 07-build_abe-glibc/console.log.xz | Bin 245696 -> 244628 bytes 08-build_abe-stage2/console.log.xz | Bin 205596 -> 204604 bytes 09-build_abe-gdb/console.log.xz | Bin 39464 -> 39616 bytes 10-build_abe-qemu/console.log.xz | Bin 32600 -> 32500 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2716 -> 2812 bytes 13-check_regression/console.log.xz | Bin 6160 -> 7876 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 30 + 13-check_regression/mail-body.txt | 94 +- 13-check_regression/results.compare | 54 +- 13-check_regression/results.compare2 | 213 +- 13-check_regression/results.regressions | 64 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 96 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 64 + sumfiles/g++.log.xz | Bin 3431876 -> 3408532 bytes sumfiles/g++.sum | 68 +- sumfiles/gcc.log.xz | Bin 3027244 -> 3047880 bytes sumfiles/gcc.sum | 5357 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037452 -> 1043016 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214656 -> 214684 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2704 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434080 -> 433284 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 3348 insertions(+), 2838 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