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 d8c84dc13a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8e07f5ebf2 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 8542fbc50d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 17e76218f7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 7f6e122b59 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 74565d2159 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 3b23f9970e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards f5af229e47 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 953a8752e6 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9f0d01a048 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 36ff6210e6 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 421d04f2e0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 1face48555 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 5ec20c747c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 14ea407a47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 95df05f01c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ddf1283a7a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 1aa1e8b768 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 2f0e5792fa 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 487dc580f5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards fc16299986 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards f7465a4abb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 10bace5932 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 45b0907198 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a404eac385 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards eb23db6a6d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 961fafd4cf 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 87ba5016ba 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3a04b227a6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 342c32aff9 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b48ccc5880 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ab0604caec 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a3ab261af8 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 51d9dc7168 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1b1a45bcb6 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 969feafeb1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards b5eb653398 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 809df0c5f7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 04b2d5da76 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards a7dc6577f4 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 627430534a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 3c8cc41bc4 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards bbf1b13c7f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 68d9d835a4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 7687bc569a 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9363d68c81 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 51d03d5ead 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 6e8c804457 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 53cadf092a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f0b08df90d 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ad21c29d08 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards ca3306a43b 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 3cf51c4439 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 8e946bb334 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 4e02dacd31 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards df2c019c55 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 8c829b000d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards af707abb9f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f86cfffd37 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards a7e1b2c250 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f934b63687 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards b1246fe3a1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 0645f54bcb 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 7131c037d9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 4ee9d2cce1 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 5aa99f64b3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards ff97c96e90 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 9dca4c9210 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 38c85a879b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 1c5cbd3ad0 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards f1b8bbcd94 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 5442e7cb44 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 961cd10529 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 83be1e8160 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards ef9e53d0c8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 649885d07a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ac2fc52990 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards b98136a0c5 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards dee16addd6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 1efa0f74e1 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 78b1453683 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 4cf8f7faca 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards c7dad99cf1 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d7101daf3d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards c4b5216d19 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards f9932181f2 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 7d4fe615b6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 1a33864775 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2b534f7b2c 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 1061560c5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 4cb74f7813 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards d3d391c042 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 1613402a72 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 9bfee03ddc 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 4b34231fb4 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 15ed3034c3 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 24ae570b0b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 3c54bdbd28 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 1013d6636d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 8b2bb73183 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e2373e7ff2 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 169b6eb11a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a4e42493a2 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 5207583f9c 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 7e1bb0644a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 4b066fdf68 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new b9c0845ff0 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c3efc78fe1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 784e9eccb6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new fa2b6aeec9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new cdf95e8dec 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new ba3b41c181 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 9cb624db2e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 66ec4e10ec 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 872b994247 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 023b9a635f 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new ced3f90276 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 03f9025908 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 97e146111b 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new c7ae9ca655 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new ce863dd0a3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ca1c6a1adf 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 36ef7a0c0a 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 18652c1511 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0514032a5c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 467788a522 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 85cb9141d6 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 9ea80651b7 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new fcd54dd025 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ca981ba8af 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 333788ea06 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 5f1b5a2167 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7c276fe7bb 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 5b228b8853 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 2ff008b72f 295: onsuccess: #2545: 1: Success after linux: 10 commits new 59ab3618be 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 9d14acbe85 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new d13bf9fa25 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ade54481b4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new c23d770a39 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 0d3b0169ce 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 834d9daea5 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 84ba5d8fab 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 3480978fb7 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new acd75fa031 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 03c7c333f6 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 9a0e84bfbc 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ec54e0c861 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 927354c695 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new dd5c22d59e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new b4911689e2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5ad9e23ad5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 939c76b7d4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d3e2b08eec 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new fe8cc35064 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new f57c7e21d4 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 8fb0325a76 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new b8d403ef8f 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new d1f2890588 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new d79540450c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new f00278af1d 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 77c84aa8af 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new ac8e865288 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new cb9d591567 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3202c0b2b2 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6e977cdd1c 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b283654e9f 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f910f7ae83 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new ab7fc0dc7e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 08448a815b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 7d6f13d611 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new faa9599d34 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 25ea36a06d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new dfa395ea16 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 46d9a2a17a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new d2fc588496 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 9b32322456 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 04af7a2a7f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 357aba965c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 95c81ab813 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new d45df33ac5 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4ef32c5a93 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 1be05ba821 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 1dde03cd59 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 916f95a94c 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d4bfdc3b47 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 587eb3f889 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new c1c612368b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f495d9eb0a 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new b7a9709216 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new d2fcdb66b7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 86776634fb 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8b526d0477 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 026bb6f798 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 4a2b902e27 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new af2436620e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 5a603c6cd6 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new ef7bbea610 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f9f137bc4f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new a950380b2c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c99f413348 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 710e6f30fe 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 7b8bee092f 363: onsuccess: #2613: 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 (d8c84dc13a) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31032 -> 31532 bytes 04-build_abe-stage1/console.log.xz | Bin 73028 -> 73368 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8888 bytes 07-build_abe-glibc/console.log.xz | Bin 244692 -> 244340 bytes 08-build_abe-stage2/console.log.xz | Bin 204076 -> 204576 bytes 09-build_abe-gdb/console.log.xz | Bin 38464 -> 38844 bytes 10-build_abe-qemu/console.log.xz | Bin 31960 -> 32020 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2996 bytes 13-check_regression/console.log.xz | Bin 5784 -> 6076 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 57 +- 13-check_regression/results.compare | 48 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 44 - 14-update_baseline/console.log | 48 +- 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 | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 44 - sumfiles/g++.log.xz | Bin 3399592 -> 3385396 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3023404 -> 3012096 bytes sumfiles/gcc.sum | 4920 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1040948 -> 1041316 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215216 -> 215112 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438148 -> 423800 bytes sumfiles/libstdc++.sum | 55 +- 43 files changed, 2595 insertions(+), 2820 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