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 bfcddcc68a 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 434ecc7660 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards b2b0dfa020 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 868680e815 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 772718d2ff 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 5f32c4e96f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f7ae308048 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 4a8d9b23a0 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards cf0a265d70 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 8029149e78 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 237c341107 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 0e99b8f560 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 5553ccd0b4 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards c6e655c7e3 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 021e569e05 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards a816394396 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 2c63950d61 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e58a6e9105 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 394893840a 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards ff8f2c1211 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards c4aa874019 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards f2807092ea 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 4b469a330d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards f411f8a12c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 0fe0748803 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards ffd0e9ebd0 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 33378a8a25 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards bafc47ef72 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards f1ae61756e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards bad99679fc 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 5c5586d0e4 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards d090bb4f48 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards a709d2dcb8 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 565e969bf3 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 4b1100ecdf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 23239b9e47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards a7292521e5 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 138c0793d1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards a0a3e315ee 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 03c1e0cb8a 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards f1aed29473 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards b4e9ec3744 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 2d86be9eb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5ea4fc0fe2 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 528919832c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 0f6881c658 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards eda4dd29e1 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards ee947da46d 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 5b3440f91c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards acee137a73 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards d82a539140 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 73a2eb762a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e5bf357026 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 966c6a9bb6 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 23f1488928 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 6834744a35 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards bb858b75ab 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 5e6ac96372 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 3947a20e84 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards dc6d356db4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b800c3f744 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 8b951b90ac 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards b9204962f2 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ef257633d6 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 9b19d472bf 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards b12a5a2d2d 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 2378239558 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards cac1251ae9 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 9edcab3010 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards c0f331477f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards c3c8548c51 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards f90634ae5e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 31888a39f0 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards e8e0d2e5f7 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards c7feb1961f 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 51f95982d4 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 38fa9638c9 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 3c2fc7bf42 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 00a3619e47 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 2709f2e649 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c245d83b89 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards a0e6ee2fc8 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 06873cb2e6 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards d4fdf55049 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards f5e468b2a9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 346c843188 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 69d688a871 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 890f315cc7 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards f5d3cd43f8 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 8d4ca5e58b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards b2f5509327 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 96b1a5515a 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 8c35945393 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards e197b6f775 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 43e2312f46 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 217b11c922 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3faa3aab00 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e35621a870 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 91eb74ab72 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 9c416d0c5e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 01e18ab2e0 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new d764b1d121 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new bbe6605593 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new b8d18a45f3 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new b7ef1d7679 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 5d1f756c42 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new b5b20bf620 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 0915087136 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new d4dd32c262 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 889c224f3a 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new e291709d4d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 12b434b260 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 36c90e36b9 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new d8593c396c 295: onsuccess: #2545: 1: Success after linux: 10 commits new 37d188d479 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 7c73e8dbae 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 90d7bf166e 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 012274bfc6 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 17a6a576a2 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 2fab25eb49 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new c2a1c3ea0f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new c665687979 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new c0df46e8fe 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a750c9c8ca 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new b0a1719f74 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 9abf3f5711 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new fd84adf154 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b9b3098493 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new bb2df13fa2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 8b2f1546e8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new ef630e3797 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 234fe3e912 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 8c89df2ccb 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 02f41f588a 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 50de3aedd1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 6c4966d1bc 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 27396676b2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new ff90e5cc59 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 6028931a95 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new ebdc816a4f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 52a598a145 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 5ee1f61517 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 62251e6b42 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 11fbed16e3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 58bd184583 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b7e05d1232 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 9c8bdb7686 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 3f7b84be2e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new daf6dea882 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 126a0f0885 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new b94ec1067c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 69727e977f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 799e464b26 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 3f6ea9dfd0 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 0fb534db8c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new f11a4cc647 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new ed44a0e840 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 43a5368c7d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 11a774926c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 10562a5687 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 856a4af6bc 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new e5d168b77f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new ca6703d6ec 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 49bd141a3d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 077b5fad29 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new d80f7fc9ab 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d20f33757d 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 9c7ba26f36 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5ca07c15bb 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 555b81f7d4 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 072088a48b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 06239b2fda 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 7ad1b40da2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new ce16f03a20 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 2642430052 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 53de8c68bf 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 88486025a6 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 7b8efeaf03 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new e7cfac680c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new cd647debfa 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 8c3b955605 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 276bdf4962 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new bf2620ddcd 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 65a5dfd5a2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 462a809702 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 552ed30fb9 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3866780151 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 6d34e66d68 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 3c7b9aa8d3 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 7680c509c3 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 75c6a48099 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new b830af61f6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new b7e6fdea75 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 03b0e6edf3 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 106c1a34f0 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 5ff7cb66e8 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 236eb35ffc 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 9ee19a024a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new ca2c8f6968 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new e2b7710924 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 9ea5c69d61 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 265e1f2847 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new cc281b1ce1 384: onsuccess: #2635: 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 (bfcddcc68a) \ 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 1772 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31456 -> 31964 bytes 04-build_abe-stage1/console.log.xz | Bin 72840 -> 72948 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 244960 -> 245376 bytes 08-build_abe-stage2/console.log.xz | Bin 204552 -> 204704 bytes 09-build_abe-gdb/console.log.xz | Bin 38788 -> 39012 bytes 10-build_abe-qemu/console.log.xz | Bin 31508 -> 31588 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3936 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2716 bytes 13-check_regression/console.log.xz | Bin 6872 -> 6004 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 74 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 55 - sumfiles/g++.log.xz | Bin 3400736 -> 3408316 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3026052 -> 3010924 bytes sumfiles/gcc.sum | 5412 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037908 -> 1036552 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217692 -> 217708 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437640 -> 434612 bytes sumfiles/libstdc++.sum | 38 +- 42 files changed, 2876 insertions(+), 3023 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