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 5bbeb958ac 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 0826ccc5f2 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 552b0e2d9e 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 9ae6eae655 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards b723ea3e71 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 57e86ad7d5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 8dd1f82600 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 0654b4c98e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 5cba6ae79d 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 6894264b82 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards bd45206f59 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 03371a0b77 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 46ce3e1e85 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 3a4cc00a65 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 12a2093f9f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards c1f3e18ed0 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards befffd0a6e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 9fc8ad26bb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 1d2d7c5e93 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 7108b36d96 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards d77d331c95 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ed0b6a6842 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 267c5abd57 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 7b0adf9979 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 5b1fefcdbc 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards da2f3d7d7f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 67c2e94514 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8d55bfa3dd 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 1245073110 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards f4cf565d29 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 5ea4a02a10 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards ee9e6fe360 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 36cd1856f5 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 8e4d849a6e 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards e54e51829c 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 498927b1f4 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 4611bacd17 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 2f4596f1e1 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 4766b45fa6 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards a3caf05a23 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards ab7ec89383 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 2a4c55266a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 8b2d8141d2 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards fb6816f033 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards b3ab81884a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards aa723fe685 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards b0fadda654 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 8b8cb45111 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards a92840fbdd 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 70c0ee67a9 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 017e875c1e 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards f841479a6f 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards ead24841f9 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards e20d693c66 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 612d3d7583 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards ebfedf9a38 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards dec5f7ed9f 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 2896661149 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 4f597f5e8e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 1e46a56c9a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards e16f8245e8 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 4d9b895b52 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 70e4ffee87 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 09a3067098 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards a59af6d692 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 3a59526fb2 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards b710f7ae3a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 1296b8723b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ed42e3b294 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 8c95af894f 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 4d7ec07c42 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 4a22260a1e 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 49238d1ffd 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 14fe69b20f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards acf4952a5d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards ce70ba8665 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 13437f498a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards aeb56dc771 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 849cf2ad85 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 19a22ec5e9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards ea36016146 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards cbf5dec350 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 227a40f74e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 698cd25e07 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 7b76d35258 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 5149590f5d 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 1e6c072724 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 76cf5bdc63 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 1a763b1434 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards a0ccf09b58 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards adf3142644 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3b24692c7c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards fbb87fbe35 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d143b076cb 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards fbc8539d56 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards de187a2106 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 54722485e2 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 2760722022 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 1a8beb3583 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 345f505e1e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards e622ec3350 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 1e7de33b26 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 52dcdeddc8 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 567016d4cb 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new b9783be7e5 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new a94c89e11e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 6d88fd1c36 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new abbf6d60e4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 5c17d744b6 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new f5a95df6d6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new f750099fc6 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7bf4687a75 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d5cc9e744d 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 448fec9661 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 9873c0695c 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 7f326203e7 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new cfa40e8ef3 295: onsuccess: #2545: 1: Success after linux: 10 commits new be471f3fdd 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 648ce6c249 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new e8096f8198 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 975fe0f8ef 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 0be06ec343 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 7dcd250135 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 57458e7697 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5a5f7a6200 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 259d74278e 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new bb90a850ac 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 236b698d0f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 5baff176ff 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 93dd8f21b5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 03c2d317e4 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 22ade3e09e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 7075e1e742 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new f748a53de8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new d68c7e05e4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 1746986177 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c69e853514 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new b453ed34cf 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 455be250a1 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 9e58aaf575 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 9983973ef5 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 370b991b8a 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 969182524f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 308c83212b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new fe37807f8b 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 0a4835e9a2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new acaeee90fd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 2d156fe24e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new fdaf7dbc71 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new b06acb6907 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 72ae828477 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 8502893bce 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new da70f38adc 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new c4c0260c69 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 9f63c5e2f7 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 135f8399b6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4fefd8f5cf 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new d5017c088f 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 6b80883ac9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 1e93a11d63 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 64e2070119 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 85f6072f03 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 83cf579b9e 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 48be0c0e4d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new c94109f036 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new d0f574c76d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 20d16cd8a6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 33a636d30a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 66b60d73e5 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d2e037e8a0 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 5b786495d6 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new d46520697f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e56126d3d6 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 10f30ef743 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new ae62eb96ac 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new e7c591e7ed 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new fd3fab85e9 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 18750f483f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 7fd3418a78 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new baf8a79124 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new e91dddbc8e 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 514a313a82 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 3080fa7b9c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 56d84fff6f 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 6713a30003 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 498011579d 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 1a0eb2728e 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new e1bb48bda3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new e99ebdf6c7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 7d3bce58cf 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new ce68fe62d4 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 843e2012ca 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 4bfc28bf21 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 45f1fd00b7 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new bb7316f432 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 1b243cd2b5 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 9cb605dfb0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 5e37f43609 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 3a1061fa74 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 097cdec36c 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 9e4bfe5605 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 3cc67f20b5 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 0d61c87f15 381: onsuccess: #2632: 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 (5bbeb958ac) \ 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 1816 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31296 -> 31476 bytes 04-build_abe-stage1/console.log.xz | Bin 73232 -> 73092 bytes 06-build_abe-linux/console.log.xz | Bin 9384 -> 9356 bytes 07-build_abe-glibc/console.log.xz | Bin 244544 -> 244432 bytes 08-build_abe-stage2/console.log.xz | Bin 204400 -> 204508 bytes 09-build_abe-gdb/console.log.xz | Bin 38480 -> 38628 bytes 10-build_abe-qemu/console.log.xz | Bin 31148 -> 31500 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3124 -> 2832 bytes 13-check_regression/console.log.xz | Bin 8256 -> 6328 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 23 - 13-check_regression/mail-body.txt | 108 +- 13-check_regression/results.compare | 73 +- 13-check_regression/results.compare2 | 219 +- 13-check_regression/results.regressions | 98 - 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 | 110 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 98 - sumfiles/g++.log.xz | Bin 3397020 -> 3394400 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3028304 -> 3017664 bytes sumfiles/gcc.sum | 3310 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037284 -> 1036072 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217632 -> 217432 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437468 -> 434728 bytes sumfiles/libstdc++.sum | 50 +- 43 files changed, 1833 insertions(+), 2425 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