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 535fe413b9 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 4823eecda9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards ab88796628 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards daa4501ddb 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 866be4dd5c 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 743e79c526 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards a5c320ee04 408: onsuccess: #2662: 1: Success after linux: 11 commits discards c5869d751f 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 2c30669f1a 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards d8adb02b92 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 2756c7cf73 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards af7e806032 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards aceb03362b 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 71c3b105c1 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 8bae9eaee0 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards c730b8fb14 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 3f8f961676 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards acc9ea890c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 8959e3ebcd 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 4535a4700b 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 4fed91c20b 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 6191c24f59 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards cc66265892 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards f316049abb 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 7a727472a9 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards de7da7ba2b 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 286dde6f31 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 44dcc2f7a6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards c376dacb83 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 5d01b64074 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 157e46f020 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 3b39e0f45c 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards cf350c3a3c 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 3ad11cdbf3 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards c5fff16711 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b3dc13a779 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 2aa2111d45 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards b2d0014e56 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 3ff7954cf8 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 856e154d49 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards f9fcbb8aa9 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards ff80609a35 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 09c929bf70 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 397cb1edbe 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards ae6247c1f4 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards a9a2b997f8 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 79cb765ab0 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 8ff2552d3e 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 047c852fb0 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards d09cc11b4a 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 37cd3fa689 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards affcb0dd9f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards b42dbf6b7b 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 383c29a7af 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards b56928509e 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f1762425cc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 4d78378496 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards dcf6a1d9ef 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 94b9bea312 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 06b75d3415 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards d985181ee3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 67c28cecb1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 2abac40762 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards d347787675 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 2084761cb1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 6397d0af90 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 1eed8680b1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 8100699850 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f48f9cdabd 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards be28a60d8f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 4de34de9c2 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 02a1336e96 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards a76b4e390d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards cd26728a7e 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 4238fe9346 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 6d84a0b328 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 6ed7f6d223 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 9d309f868b 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 553afc2527 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 332fd315fd 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 50437c1f01 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 1a10b6123f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards e601e4dd9e 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 50384de8bc 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 513f0ddf12 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 65b87cb52e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards d6958963c5 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 9a82256d54 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 8679e18b13 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c022dd0a1a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0b1922b180 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 88fdf2b761 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 2d1c37daa6 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards b50b8910b7 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards aabcc01d71 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 0aa8ca82dd 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards bf78f5e330 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards edfc490840 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards acb0a56c81 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c6e3f86739 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards fd398a6921 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new ff72d076a1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 1072219997 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 1284d402eb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new df1eb825f3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 6783134a14 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new f2f87e7b93 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 91f3056174 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new fa045044a3 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 5fa54e8b22 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 36669e1199 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new b29b4765fc 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 060413780b 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 5d6e993abe 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b3211d9afa 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 834cfaabc3 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 729a69c91e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 1e5ec1ca14 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e289040be3 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 85f5f6f05a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a9a36180c9 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new b308fc29df 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4a82bbed08 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new c29aff7365 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ab366afac9 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 5a13aa57ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 123d9b88b9 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 2fc4f991df 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new b41a08a9b7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 36b4aad41b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 5394e6403c 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 8badf82386 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6f0782e86c 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 98af61b11f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 12a386128a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d11c42fe58 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new e912e34350 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 0dc5c7c119 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new be0823290c 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 8f2e9392ff 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 2eb03537e2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new d5d1c6501d 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new dfa1a6e2f0 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 1fe2830107 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 336c1832b2 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new b2c692e888 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ba46ec3dbe 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new aef425c77a 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new acb013ae03 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ee9cd37b29 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new ae604ebc66 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 2a939e78d2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 63afcbc741 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 5c4953b360 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new f05d236861 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new da92000e8b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 6edae7eb53 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 7dbb0af0be 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 00eb550a16 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 39a9ce99f2 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new bb84f7acf5 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 3b8fefe59b 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 72d2b40a7b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new a75f4ae034 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new f722fdb7f7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new c792e632b9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 0205af0684 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new adf91e580e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 1e5de3c437 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 0123a7b507 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 1369a1e47c 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 700b4382f3 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 2f1b9b289f 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new f71092aeb0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new bea9977bbf 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 8125bf078c 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 25f9a38846 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new de46df6408 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 2b6661feb0 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 39b86bd60d 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 43e55b0822 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new bb5f99e30d 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 35f47f95b6 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 3a9ec7efb2 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new db19a990cc 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new f5d64da0d6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 6152fe63e2 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 6d00f0d1fa 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 5c3dcdc188 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new c52eaac16a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new ef1e2dbc75 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 6cfa23270c 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 416a44c2dd 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new ad7b62add0 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new cd96086285 407: onsuccess: #2661: 1: Success after gcc: 7 commits new dae39ce1e5 408: onsuccess: #2662: 1: Success after linux: 11 commits new b4174b5fc5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new dc6d39c79c 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new ecdf92b62a 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 5038399d73 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 8b25d4376f 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new b0a1416625 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new de16e64744 415: onsuccess: #2670: 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 (535fe413b9) \ 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 1788 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32028 -> 31508 bytes 04-build_abe-stage1/console.log.xz | Bin 70800 -> 70668 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 243304 -> 243556 bytes 08-build_abe-stage2/console.log.xz | Bin 201888 -> 202616 bytes 09-build_abe-gdb/console.log.xz | Bin 39512 -> 39184 bytes 10-build_abe-qemu/console.log.xz | Bin 32508 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2688 bytes 13-check_regression/console.log.xz | Bin 7136 -> 6992 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 21 ----- 13-check_regression/mail-body.txt | 74 +++++------------ 13-check_regression/results.compare | 43 +++------- 13-check_regression/results.compare2 | 138 ++++++++++---------------------- 13-check_regression/results.regressions | 65 --------------- 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 | 76 +++++------------- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++----- results | 65 --------------- sumfiles/g++.log.xz | Bin 3397504 -> 3414240 bytes sumfiles/gcc.log.xz | Bin 3023124 -> 3015800 bytes sumfiles/gcc.sum | 47 ++++++----- sumfiles/gfortran.log.xz | Bin 1034140 -> 1042308 bytes sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217508 -> 217604 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436232 -> 436936 bytes sumfiles/libstdc++.sum | 38 ++++----- 41 files changed, 216 insertions(+), 487 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