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 a0e53403ac 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 0162281c13 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards c2d5ce3f6a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards e675a59b09 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards f692fa7842 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 738fe8c14e 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards c545f2142d 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards ca9faea0c6 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 62ef47fbbe 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 016dcc5395 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 2c6d25cd31 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 8da0937ddb 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 744fc0e70b 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards a79e9d72b6 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 996ceb1bfe 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards e9fbccf603 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 488de03f21 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards ff4576d01a 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 55f82f4701 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards f9519002e9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 4f0e80039f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 501f658555 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 5b4db5e2c8 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 448ce0e924 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 7e8761bb92 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 2a9bff6a7d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 566ee1bc18 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards fc1381c82f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 43f3861101 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards c71c140b95 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards e8bd5e11f3 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards e1394e88d1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards d6125c42e0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 18aedf438d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 85839192df 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 9da1185c6c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards a12264adc5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 3a1d43bcd7 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 65fed72d0a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards c627acd062 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 2a545db731 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 47b39075d2 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards a3ca724826 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 32fc28c7f9 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 06f56cee83 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 38a691b568 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards b56445f130 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 652551baa9 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f4ce35766a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 50cac35691 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 97c5f1435a 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 9b26194715 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 8901d5b01d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 55d98a2568 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8af8b02aa2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 7287d92ea8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 08004fcdee 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards f707d324ca 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards da75545164 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 729386c377 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 5c5eb38891 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f1ba88ddf1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 896b3f6ed5 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 6fb573b4f6 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards b1f7409a02 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards e5be5f0ae7 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards aae379a1eb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 14c5d673ad 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards d17573f192 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards e136ec1b57 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d464f06c00 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 60762a8f67 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 6b6f29297e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4073836dfc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 25b290b15c 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 21e9ccf313 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards f700d8bbb4 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 224aeed562 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 3b1d73fd71 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 859a4d7b25 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards c53a9622a2 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 9730805c89 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards e5eb05fe19 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 6acbc6168d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b2fd7a004a 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 59cbf05da5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 22784c051d 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 8317d37abd 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards f65351ab8d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 0a6e3129ca 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 01dc030a8f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c13453ccf0 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 9c1d3633c9 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards a2331974f7 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 43e99b5c81 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 60fc7ac345 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 838304a520 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 7b31b4c7fb 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards e7d50ef76c 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards ae4111fc12 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 114b292de9 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 04341789d6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 9fd83eb3b5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new c705ad4209 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new e5b99d2a04 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new a333a0f5c9 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 017960c603 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 5f5640f049 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 1f1859487f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 6df3af779f 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 60d291459b 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 9ddf8de4ec 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 0adfbf4863 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new b930c37b13 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 3040f9d486 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 506e61285c 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 07c3a1ea73 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 8fdf6ff719 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 2e49424ff8 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 51acda3c9d 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new aa9b4c091c 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 75a5f38800 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1530b03805 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new e99410dc96 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 62b8cbe318 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new e1612562a0 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 1860a8bd6d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 2d37122e35 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new ea10a0cb21 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 997c0dc571 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new ea820807a7 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 77152ddb05 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new c026025e10 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 6d9d47a956 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 8df7254c60 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 4dcfd38ffb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 495d8fbda9 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new cf95e7a7fe 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new a28918649e 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 7d66cdd44a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 42a0c50cc5 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new d54365cfa0 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new da475cf81f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new b3b2fa3c6d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 0280e66264 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 0a554d6a0e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 0579cfcd4b 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 52817ca956 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 4eaad14073 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 7560a952bb 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new e977ef4bb0 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new e0acef8036 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new f60aea8274 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 256ebe9f07 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new a6098eadda 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 0261c05707 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new b9641fb5f5 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4aced0f9cd 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 3ac587245c 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 585f6ec50f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new ab956d18cd 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new f207c14d37 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 7079169a19 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new b3abf6674a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 85ff94b1af 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 0e203a1699 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 4081bd9997 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 85fe0b27e9 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 10f86869cf 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 1cf6767184 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 7f69fba199 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new ce938f2e70 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 80cdcc2f01 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new ddee30683a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new b82d169697 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 6189c891e0 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 647525eab3 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 84dff88a59 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new a3fefa4873 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new b4c9992728 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 6832aed883 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new b2e92f5ed5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new afd6568262 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 43669b835f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 6eb9d536b3 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 8aad132252 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new edf59c921f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new ca80757b74 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 1d4c215331 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 5719e9b68f 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new b9c3d09e62 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new d6bef9a03a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 372cb4fff7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 18f5e7556e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 5ce422ed52 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new b77506ce77 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 37a8146e0b 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new abdfd39357 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new c223241dc0 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 2f8ccb076e 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 8e9adec227 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 1665cf8fe2 407: onsuccess: #2661: 1: Success after gcc: 7 commits new c45faf157e 408: onsuccess: #2662: 1: Success after linux: 11 commits
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 (a0e53403ac) \ 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 1800 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31136 -> 30940 bytes 04-build_abe-stage1/console.log.xz | Bin 71416 -> 71076 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 243504 -> 243848 bytes 08-build_abe-stage2/console.log.xz | Bin 202388 -> 202748 bytes 09-build_abe-gdb/console.log.xz | Bin 38908 -> 38660 bytes 10-build_abe-qemu/console.log.xz | Bin 32276 -> 31580 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3832 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3028 -> 3012 bytes 13-check_regression/console.log.xz | Bin 5896 -> 5756 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 13 ------ 13-check_regression/mail-body.txt | 71 +++++-------------------------- 13-check_regression/results.compare | 39 ++++++++--------- 13-check_regression/results.compare2 | 59 +++++++++++--------------- 13-check_regression/results.regressions | 49 --------------------- 14-update_baseline/console.log | 64 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 73 ++++++-------------------------- mail/mail-subject.txt | 2 +- manifest.sh | 22 +++++----- results | 49 --------------------- sumfiles/g++.log.xz | Bin 3385072 -> 3401596 bytes sumfiles/gcc.log.xz | Bin 3027204 -> 3014124 bytes sumfiles/gcc.sum | 28 ++++++------ sumfiles/gfortran.log.xz | Bin 1038268 -> 1038592 bytes sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217536 -> 217504 bytes sumfiles/libgomp.sum | 7 +-- sumfiles/libitm.log.xz | Bin 2664 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432596 -> 439008 bytes sumfiles/libstdc++.sum | 56 ++++++------------------ 38 files changed, 145 insertions(+), 398 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