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 bdb4666bbe 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards acf8a3b69d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 6a46a6c2a3 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards bddce72e7a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 307a140ed9 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards ff9fd328b7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards bbd107bf72 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards a9892a0296 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards de3f4162cb 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 9ff20934ef 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 07d69370a3 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards c51659580d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards fc3475edc8 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards a073acc309 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 4616df6ffc 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards ae8b8d1baa 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 8fe6715de6 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 4cbe0212fa 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 658bdea025 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 678cc02ee7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ffd66daafa 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 941afc7c2d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards b588f3b040 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards fc4391b706 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 27c1021ac4 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 96cf3279fa 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 3148e4a52e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 5414f095c3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards b03b3b5465 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards fe19fa3390 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a728eb82b8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards accd019e91 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 3fd8b58d49 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 6fdf1a5ef0 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 21a1e52939 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 46c040c303 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 5f288eea3f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards a76da63995 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 14613dae91 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards c9e211c6ee 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 98b3cb9dc4 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards d94c37c221 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards bd0895ae3e 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 3fdd78a000 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 90fb643e51 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards e1e3730d6e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards e2cca73ecf 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 09da99620a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards feb8364e1a 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 59d6911bde 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 2ef74c24e3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 7da9f25c06 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards d57a919f59 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards fe0781c137 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 77f2ce2885 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 63c4281419 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 7107ac89d0 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 268a2a2167 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 2d052e6cee 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 4426b7eeef 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards a725d4a64d 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards fcf63a965a 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ca7fe30f91 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 71527eed1a 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 1ad46d25f6 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards cd2d698900 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards f727e54ae9 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 019e81883c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards aa8f5e2ae5 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f69c415576 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 939efe0a46 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards f20eebd32d 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 7c252a462b 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 0f8e4151f6 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 6759d95281 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c61f3a20da 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards a73478d0ff 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards ccb84e8ae4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 246c910b05 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 8d74fc9fbd 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 7897de9df3 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards bc63ecf88b 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 2924af6f4a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 2c1b9a958f 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards e6fe120172 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards c9fc306fee 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 761790fac4 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards fee9833e92 295: onsuccess: #2545: 1: Success after linux: 10 commits discards f0eb80c855 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards a6716a06bd 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards c2ecb0aaa5 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 62af13452c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 5d7ea04292 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 5f0c19c26d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 80e4c67a38 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards f8a0ca15f1 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 71d01825b2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 79b0b6d80b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 92f808a1d3 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards fe8a455cb4 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 1e2ee87395 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new a895ed9a65 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 01e18ab2e0 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 9c416d0c5e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 91eb74ab72 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new e35621a870 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3faa3aab00 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 217b11c922 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 43e2312f46 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new e197b6f775 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 8c35945393 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 96b1a5515a 292: onsuccess: #2541: 1: Success after binutils: 13 commits new b2f5509327 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 8d4ca5e58b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new f5d3cd43f8 295: onsuccess: #2545: 1: Success after linux: 10 commits new 890f315cc7 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 69d688a871 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 346c843188 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new f5e468b2a9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new d4fdf55049 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 06873cb2e6 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new a0e6ee2fc8 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new c245d83b89 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 2709f2e649 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 00a3619e47 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3c2fc7bf42 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 38fa9638c9 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 51f95982d4 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c7feb1961f 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new e8e0d2e5f7 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 31888a39f0 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new f90634ae5e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new c3c8548c51 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new c0f331477f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 9edcab3010 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new cac1251ae9 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 2378239558 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new b12a5a2d2d 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 9b19d472bf 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ef257633d6 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new b9204962f2 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 8b951b90ac 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b800c3f744 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new dc6d356db4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3947a20e84 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 5e6ac96372 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new bb858b75ab 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 6834744a35 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 23f1488928 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 966c6a9bb6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e5bf357026 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 73a2eb762a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new d82a539140 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new acee137a73 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 5b3440f91c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new ee947da46d 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new eda4dd29e1 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 0f6881c658 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 528919832c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 5ea4fc0fe2 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 2d86be9eb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new b4e9ec3744 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new f1aed29473 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 03c1e0cb8a 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new a0a3e315ee 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 138c0793d1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new a7292521e5 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 23239b9e47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 4b1100ecdf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 565e969bf3 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a709d2dcb8 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new d090bb4f48 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 5c5586d0e4 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new bad99679fc 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new f1ae61756e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new bafc47ef72 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 33378a8a25 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new ffd0e9ebd0 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 0fe0748803 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new f411f8a12c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 4b469a330d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new f2807092ea 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new c4aa874019 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new ff8f2c1211 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 394893840a 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new e58a6e9105 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 2c63950d61 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new a816394396 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 021e569e05 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new c6e655c7e3 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 5553ccd0b4 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 0e99b8f560 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 237c341107 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 8029149e78 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new cf0a265d70 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 4a8d9b23a0 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new f7ae308048 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 5f32c4e96f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 772718d2ff 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 868680e815 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new b2b0dfa020 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 434ecc7660 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new bfcddcc68a 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...]
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 (bdb4666bbe) \ 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 1812 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31680 -> 31456 bytes 04-build_abe-stage1/console.log.xz | Bin 73280 -> 72840 bytes 06-build_abe-linux/console.log.xz | Bin 9204 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 244764 -> 244960 bytes 08-build_abe-stage2/console.log.xz | Bin 204684 -> 204552 bytes 09-build_abe-gdb/console.log.xz | Bin 38764 -> 38788 bytes 10-build_abe-qemu/console.log.xz | Bin 31444 -> 31508 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2912 -> 2660 bytes 13-check_regression/console.log.xz | Bin 6468 -> 6872 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 55 + 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 67 +- 13-check_regression/results.regressions | 55 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 57 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 55 + sumfiles/g++.log.xz | Bin 3391748 -> 3400736 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 3024228 -> 3026052 bytes sumfiles/gcc.sum | 4602 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1035136 -> 1037908 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217544 -> 217692 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437016 -> 437640 bytes sumfiles/libstdc++.sum | 31 +- 43 files changed, 2696 insertions(+), 2418 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