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 6e3a3834e5 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 4234047b44 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b3d2dce0b3 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards b0885bb454 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 466c38b414 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 8db555b141 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards acca97576c 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 4792968129 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards ab1e91a63c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards df339735f8 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 3544c0fb5a 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 1295d3a1a3 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards eed74caab8 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards c7a0318abd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 1a8439a779 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 7eeec0f21e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 515c395c10 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 164b25aca0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 336db6b724 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 6851494bbf 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 9c5c2bd8a6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards e273214476 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards db83092faf 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 1a4375f4af 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 774dbc36fa 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards ff0e533a12 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 9bba18e2e9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 109f6d0594 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 994858f28a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards ee9a44167d 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 470786b8c5 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 3ab5f97534 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 376b63ec71 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 0e68abf445 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 08c7d807c1 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 8a20661e30 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 3176b95606 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 092c8b28af 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 2c280cc53f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards b0340305d1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 526a816616 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 6d3a974be0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards b515679fd1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 344c3afdcf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards a26ce1da1b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 273a6c9ceb 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards a49930b84e 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards b6f8c013a2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 551b6a2971 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 0577070964 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 650d3cd053 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards bdaa08cef9 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 33af449572 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 7a19e11fe8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 309bf427d1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards ae83929b64 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 6c9d5db084 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 57709eeb1a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 60b1d24e4f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 2a107a6c21 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 7e97fb6531 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards cc6d2fb8e9 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 918b769835 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards b4d09e4cf3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards d37f5a71ac 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 549c6f4a08 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards f1729e3d81 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 9f6bf8d253 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 9f6e2960c2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 6d57f682b3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 89297fdf1f 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 718ca49e47 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5db3881a2e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards d5c2cbe361 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 14022ba143 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ab4a058dfe 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards bea0d4d460 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 8a06134e74 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 4b20e221dd 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 179bd1c755 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 39b93c4849 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 5bb720906d 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 06563524df 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 728c3a1f41 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards ac33a5a469 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 2cdedb17d8 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards f433d36689 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 0f13bd709e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 5b17a33355 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards dd8b3b0f2a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 6ceca6d1bc 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 5437a71f7e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e2a135e620 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 002b5cfca1 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 2b9420ec64 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 26d6dfe74f 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards ea05c41682 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 4c19afc331 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 493b4d96e1 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 363f04141e 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards b9321c42ff 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 03bf3d3f71 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 68edefb239 293: onsuccess: #2542: 1: Success after gcc: 5 commits new b7d480283e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 60cb6e7003 295: onsuccess: #2545: 1: Success after linux: 10 commits new 084b565790 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new a5a765a8bb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 6cea333c45 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new feb9b4247a 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new d554a70724 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new df4189a200 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 0c135a4280 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new c8183f9521 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 19bb7f830f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 1e28e5d69f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 8d06762f88 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 633975c44d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new f17b28de14 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 23dd61e9bf 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 989b4fef40 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 7277881781 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 9d0dfec783 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 902b557df8 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 93a044241c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 2d25c47f8d 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 98914b35a1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new ff8a8aacaa 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new fef0a9d3a2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 355392176d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 42bc6f1eda 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 5faf509383 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 06224eca96 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new cfdb4a4656 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 6b670ce323 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new e5e5f00d5a 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 93be0a932b 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 2d980cdbed 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new b62db5e393 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new bd94a609ee 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new e01b8b7506 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new ae53e22c94 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 80aa266ce8 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new eaea5621f8 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 5d023de303 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 9444f6a5a4 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new afbd64d2f1 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d7e1525f32 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e77b076844 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 811d8ec6ce 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new a4e0432ec0 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 41d838e3f0 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new ecbdfee09a 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 73a9676a28 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new f2cfb1ea0d 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new f75dd51349 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ca719476f5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 0113361e0c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d2ceed6f7e 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 272f2c97ee 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 456decf138 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 6e26fb2734 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 90570d089b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 9687fd383a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 5ae4151e68 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new c3304d95e7 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new c1838be17b 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new b8058faa75 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 9dc6bc3d85 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new c220405985 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 5e76a9ae54 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new faa7bdf216 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 532e828c52 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new f683f39b67 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 9fcfb4b057 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 5da64fe4e5 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 77ead7ba3b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 88117ed59c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 8f54fa26c5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new d3fc3f5bc7 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new b2236a28d0 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new b9885757a5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 029c2d8d42 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 1487ddcfe7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 1bc37e3eb8 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new ec72f2d75f 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new f0c8a5aedb 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 1483a0962b 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 9c51358a54 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new a16caa9cf3 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 676746667d 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 8bac394bd9 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new a55f2aca0f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 0a2690d432 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 7057df565d 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new e53449b702 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 62a33d46e0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new fa8678f78a 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 253ae2c402 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 8e62f715fd 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 0760f2ac6e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 3abbbccf0a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 0e3c83bcc4 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new a7af40e369 393: onsuccess: #2645: 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 (6e3a3834e5) \ 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 1788 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31160 -> 31284 bytes 04-build_abe-stage1/console.log.xz | Bin 73348 -> 73516 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8932 bytes 07-build_abe-glibc/console.log.xz | Bin 245328 -> 245100 bytes 08-build_abe-stage2/console.log.xz | Bin 205208 -> 205364 bytes 09-build_abe-gdb/console.log.xz | Bin 38468 -> 38676 bytes 10-build_abe-qemu/console.log.xz | Bin 32352 -> 32572 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3944 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3192 -> 3072 bytes 13-check_regression/console.log.xz | Bin 7940 -> 6400 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 | 54 +- 13-check_regression/results.compare2 | 108 +- 13-check_regression/results.regressions | 55 - 14-update_baseline/console.log | 62 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 55 - sumfiles/g++.log.xz | Bin 3411724 -> 3408192 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3016088 -> 3014212 bytes sumfiles/gcc.sum | 4297 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1040308 -> 1033620 bytes sumfiles/gfortran.sum | 9 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217612 -> 217540 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437736 -> 429844 bytes sumfiles/libstdc++.sum | 54 +- 43 files changed, 2326 insertions(+), 2555 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