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 8ada807f87 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 799d97e32f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards d6456dc78d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards eac8217f48 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 826653ccb0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 328c9499b9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 87e09a134b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 06e91e9191 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 4aa7952666 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 4fd2ec7c9d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b83141a39a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b43ecc74e0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards d86580a233 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 7ae3487672 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards b891fe0192 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards b958ab9074 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 2218cab0f2 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 6b566bea71 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 39ff382a69 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 7341cd9e1f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 748e80234a 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 9f93a0460a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards d879e4321e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 649baf8795 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e9a8ff4f33 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards a2c9394770 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards d525cc7d41 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 1be5cd37f7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ea9f7e7e25 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 00d8b6842d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards fd470b192f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 705c5c21fd 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards e1ac0eb9d8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 03a2589a9c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a2ea60cf5e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 21009cf8b4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c77ea37082 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9e2b4656b2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a87fe70aba 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 4de93a6d69 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards dc56f9f29b 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 79a62997d8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 74feec7ba4 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards cb005eb599 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards efc17692ee 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 057623b500 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards c3c6252ffb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 63633cf31e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards ee89b87926 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards f999cfbc45 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 3317c14c2c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards cbee9ef73f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 0df4348ac7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 1f905d84b4 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards a4d0f846ce 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards e3a3751e11 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards c8b8ae8401 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 03cdd40692 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c96f993569 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 348e263362 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards d68f8df3b5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 8abbcadfd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0ba167704d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 7800ba34fd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards cec431ec20 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 1185ccc3dc 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 8d258b8ca1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b48b6802a7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards b8d3b6d159 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 3d0b591266 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 87fb7a44dc 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 1717b43363 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 73883025bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 2a6fdbba48 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 25e4a27362 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards f2cfd16da0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 9746ffee18 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards fffc229a82 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 737fdf4b04 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards def0cfa9ec 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 19b0547edd 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 4e18e816fc 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 9710536338 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 91b32de386 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 962450a72f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards f2fe4c75de 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards cf24cecbf8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 4ea69b3b68 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 105fca6fa1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 057cb57606 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 17f19e621a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4026ba45fc 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards e9693a0193 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 85c772a7ba 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 2ed618cb48 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards f9371893fc 295: onsuccess: #2545: 1: Success after linux: 10 commits discards f8878659ba 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 687ea7e20b 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 6eb41c4755 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 6fc1fe9e4c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards e4fb9e024a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 0bfe010254 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new cacbda0775 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 533fce475f 292: onsuccess: #2541: 1: Success after binutils: 13 commits new bde0fc0cdf 293: onsuccess: #2542: 1: Success after gcc: 5 commits new fb0ca36284 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 04674562eb 295: onsuccess: #2545: 1: Success after linux: 10 commits new 4d99fb18b8 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8a6accfdbb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 125d151889 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new facfaf5df8 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 3249e156bc 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 4a2ab8ce57 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 15c3fcf8cb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new bf0a406735 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new a497e6eeab 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a429691b7f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new fc87e53659 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 170f82179d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new d0a2c7f706 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 2291fa8554 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 07127089cf 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new da71d97122 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2ff49294cc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new a750cf51ae 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 9485d97196 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 73cd42ea94 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 44b143b11a 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c980ed00e2 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 4b502722bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 29e30a419d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b6287e386d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 2ee8d98633 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new bcde344076 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 01ffe69fab 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 4920075db7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 1112ed54f1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new a33a8e395f 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ebe78d54c2 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 2e101dad29 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new fbf6c6d249 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f87f971cea 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 1ff192f746 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new aeae356534 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new fba47f1cc4 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new dd0f1e5399 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 220e195c1a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new db6f8c7df4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 04a46de034 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new dabdab4d46 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 96d35fd18b 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new c35bf15f7a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e0cc8bff1c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 6c74d52c55 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new bc5cd3755f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new ee58347199 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 333218f72d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 51c17f5d8f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new b378eded33 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 1392963447 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new bc0244ade8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new c71f75d2f7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 67f2e4a8d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a07395e783 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d0c50ece43 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b67d5908bf 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new b89dd1185a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 7264bdc037 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new a7fef0718e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new bd2ffa68d3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 83616bdc34 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 03efe62e92 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new cd9f7eb5c3 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new f2088c18cf 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 027fc176ae 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 83ccfc56c8 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new b26d9af017 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new aa470448be 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new a473bc7cab 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new aeddfb361b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new f04e47921f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new d4c03a7e8e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new ebfd52165c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new ba6b121a84 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new a09654c26f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new cac9396ae7 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 08a39584b1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new b53cced8d3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 96c218b75d 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new e14dfb30c2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new fc0cc2673a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 6a9e95a590 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 01c9a33c82 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new ec4d6d767f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new df091d9fb3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 728ccf4ab9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new aace75ac77 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new f94a1dc72b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new ba0becc269 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 55c08af12f 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new fc0a1e375b 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 4c20bbcc75 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new dcba9c120f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...]

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 (8ada807f87) \ 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 1792 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31208 -> 31184 bytes 04-build_abe-stage1/console.log.xz | Bin 72960 -> 72888 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 244424 -> 244556 bytes 08-build_abe-stage2/console.log.xz | Bin 204296 -> 204244 bytes 09-build_abe-gdb/console.log.xz | Bin 38712 -> 38460 bytes 10-build_abe-qemu/console.log.xz | Bin 31516 -> 31348 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2796 -> 2752 bytes 13-check_regression/console.log.xz | Bin 5900 -> 6316 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 23 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 72 +- 13-check_regression/results.regressions | 43 - 14-update_baseline/console.log | 64 +- 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 | 43 - sumfiles/g++.log.xz | Bin 3394120 -> 3376764 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3018372 -> 3022220 bytes sumfiles/gcc.sum | 4484 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1035412 -> 1039484 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217596 -> 217532 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436124 -> 434832 bytes sumfiles/libstdc++.sum | 50 +- 42 files changed, 2433 insertions(+), 2532 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