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 cc281b1ce1 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 265e1f2847 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 9ea5c69d61 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e2b7710924 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards ca2c8f6968 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 9ee19a024a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 236eb35ffc 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 5ff7cb66e8 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 106c1a34f0 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 03b0e6edf3 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards b7e6fdea75 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards b830af61f6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 75c6a48099 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 7680c509c3 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 3c7b9aa8d3 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 6d34e66d68 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 3866780151 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 552ed30fb9 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 462a809702 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 65a5dfd5a2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards bf2620ddcd 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 276bdf4962 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 8c3b955605 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards cd647debfa 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards e7cfac680c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7b8efeaf03 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 88486025a6 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 53de8c68bf 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 2642430052 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards ce16f03a20 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 7ad1b40da2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 06239b2fda 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 072088a48b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 555b81f7d4 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 5ca07c15bb 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 9c7ba26f36 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d20f33757d 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards d80f7fc9ab 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 077b5fad29 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 49bd141a3d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards ca6703d6ec 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards e5d168b77f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 856a4af6bc 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 10562a5687 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 11a774926c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 43a5368c7d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards ed44a0e840 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards f11a4cc647 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 0fb534db8c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 3f6ea9dfd0 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 799e464b26 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 69727e977f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b94ec1067c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 126a0f0885 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards daf6dea882 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 3f7b84be2e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 9c8bdb7686 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards b7e05d1232 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 58bd184583 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 11fbed16e3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 62251e6b42 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 5ee1f61517 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 52a598a145 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards ebdc816a4f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 6028931a95 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards ff90e5cc59 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 27396676b2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 6c4966d1bc 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 50de3aedd1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 02f41f588a 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8c89df2ccb 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 234fe3e912 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ef630e3797 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 8b2f1546e8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards bb2df13fa2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards b9b3098493 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards fd84adf154 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 9abf3f5711 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b0a1719f74 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a750c9c8ca 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards c0df46e8fe 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c665687979 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards c2a1c3ea0f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 2fab25eb49 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 17a6a576a2 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 012274bfc6 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 90d7bf166e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 7c73e8dbae 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 37d188d479 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards d8593c396c 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 36c90e36b9 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 12b434b260 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards e291709d4d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 889c224f3a 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards d4dd32c262 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 0915087136 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards b5b20bf620 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 5d1f756c42 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards b7ef1d7679 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards b8d18a45f3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards bbe6605593 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 197f5ec45d 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 5b9dbb144b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new e7f9fa213f 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 7f3a5dbf00 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new fd1e59c969 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new dba36dcee2 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new c890bdf74d 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1a2e46deab 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 47b514f37a 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 2ba90fe3f0 293: onsuccess: #2542: 1: Success after gcc: 5 commits new c52618ce62 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 3b901e91b0 295: onsuccess: #2545: 1: Success after linux: 10 commits new 46e816a9fa 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 0b6930f763 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 41d04860cc 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new b186581991 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 033f862c36 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 374e8fe046 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new e2b43d1c39 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 4803712119 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new abdd0bb94e 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new ff75c0003b 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 17d3a658a0 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new d58d312f3f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 27a4c1f9ea 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 2f28c45b5f 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 3320f6357f 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ab2870f83a 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new be3559c418 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f839da9447 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 6c546688da 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 65e57e7a52 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new b5137b2450 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 97a282ff71 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 26ce19b75d 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 3b46fef95c 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 0ff75a2be6 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 6e5590716c 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 309548a497 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new f09876e4c3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 5e16f8760d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 632b2c15d8 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6ba296dc68 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new adcc0104ef 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 83d7d330ec 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 8afa1a293d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new e14910719a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new abb1d8075e 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new f9eb38c9ad 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 0105224b07 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new e7f2ce2a52 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 2e40228038 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 56e3ac5c8a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ca6a7de4f0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6c302ab3ab 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 63d049ac43 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 75b12e90d6 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a7ee15b97e 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new f4364090cd 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new de1855ed5a 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new eb22d85e8f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new b4e1fcb07d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 85db4041cc 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 7296a7c705 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new e3e3b31662 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new beb8da2c58 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 88510f1557 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new bf08577e10 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 6b380bf44a 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 4dd79ab51b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 1bd9059367 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8c9946dc14 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new bceeca82c6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new ffae31ba2d 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 3f29677dcd 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new b6373807ce 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new b7d7c80644 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 6f425b251c 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 8969b323cd 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 9b6cac3f09 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 980a5a719e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new a1ce02331f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new dd122b012f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new e80325d5ea 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new f30430a34c 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 8db27b3ade 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 3f1ed591ac 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 6fd96ee1df 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 00c8d7460e 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 2b0eb5a01d 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 0b95b0f5ff 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 565a902f04 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ff503de6ae 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new adb91d158a 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 2404ed3b16 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 9999eb775c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 3814cf1f8e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new dff5e9a053 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new dce2839b00 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 9c7f17dccf 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 19ea960744 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 5aa7287c72 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...]
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 (cc281b1ce1) \ 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 1808 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31964 -> 31264 bytes 04-build_abe-stage1/console.log.xz | Bin 72948 -> 73616 bytes 06-build_abe-linux/console.log.xz | Bin 8680 -> 8672 bytes 07-build_abe-glibc/console.log.xz | Bin 245376 -> 245396 bytes 08-build_abe-stage2/console.log.xz | Bin 204704 -> 205112 bytes 09-build_abe-gdb/console.log.xz | Bin 39012 -> 38448 bytes 10-build_abe-qemu/console.log.xz | Bin 31588 -> 31688 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3936 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2716 -> 3324 bytes 13-check_regression/console.log.xz | Bin 6004 -> 5964 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 71 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 52 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 71 +- manifest.sh | 32 +- results | 26 + sumfiles/g++.log.xz | Bin 3408316 -> 3417028 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3010924 -> 3023156 bytes sumfiles/gcc.sum | 4803 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1036552 -> 1044640 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217708 -> 217592 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434612 -> 435536 bytes sumfiles/libstdc++.sum | 32 +- 40 files changed, 2613 insertions(+), 2624 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