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 eaf5d92c01 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards d766cec4c3 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 30ab3aa84a 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 615b4f3dcf 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 7c753db49d 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards f7e59e4759 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards fdda783563 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 4091937df0 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards ca8616db95 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards a3519c9ddd 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 4b0451777e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards d877be6fe9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 4b64979b61 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards d3b10dc187 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards b099ae732d 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards d25bd4573e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards f9f691ca8a 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 5ae3d1b0b2 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 58dcf35e66 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 3611527d2d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards cc2e9e56df 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards edb0ee109e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards ce734434b7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards f5906f2efe 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards dafb13f4bd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards a13594a931 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards efffec22ef 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards c347bd46df 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards c71d75da3c 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards bd83c69dc5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 4e27ae47af 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 8a97e7b49c 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 562fcaaa39 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards a3ba80d54f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 8f9a7a8984 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 2f8a7496ef 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards cf00408ee9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards c1ff721d39 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards aaab044c28 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards e2e6513cf9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 5ae1da5cbe 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 3be70da5a5 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards abc59c80a6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 6c87cfdacc 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 3308f07aab 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards d0dbc12a4b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 6ede603199 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards fef79c2c36 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards d316a7d759 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 80843f45d2 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards bf487234ba 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 2a238246af 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 85c602c3e6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 57b0247659 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 902cc19755 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards b859501f12 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 64cca71f2d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 0ecfd45b53 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 675d2a61a7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 517b5cd6b1 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 0ddffe83f2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8953053f80 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ac21cca516 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards c8a665a915 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 3856a8e7ac 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7acf127e2d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9567f08645 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 4c2eccc105 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards d476f4a3e4 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 9f304afc8b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 473c67bfb1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 04b7024ebd 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 7347586982 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards e72a555308 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 29c7b95497 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 33e40cb636 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards bb610a1f09 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ea6fabfefa 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 099007a9b4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 89367df106 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 7235436031 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ed507a208b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d873519e95 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards ef31a9b070 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5f5a304541 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards beb4089bc7 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a5f6c5c1ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 0c193fb207 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 86ee04c40a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 49e75a728b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 905f796ab1 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards a676957b98 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 92c5e3b61a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 595c107bbd 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a876543892 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards c71a934b49 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1c2d0d4a65 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4b65b67241 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 4993d7aaf8 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 05dd1062a5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards d2c034f409 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new b948073e92 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 09e578b922 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6fc02514ad 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5dd95c04df 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0ea944a8a5 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 5d3bc64734 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 89f90ef898 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new d49262508c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 93388fbaf5 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ac0109f05f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 3f5abf2f59 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new d3de09e1ee 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new b9089892fb 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e3183d4a08 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6cf02bd0f8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 28c4d5f85d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 1770a8c2e9 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e9259f9835 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 5a2d719d86 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new a112bbb71d 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 804b105018 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 29f4354356 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 56b7a3e830 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new eb465e5806 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new fa954d619f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f6880607af 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new ebc22e4d8e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new aff847cfc9 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 6d75a065f8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new fb4cf60331 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 81214095ff 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 23dd0b73ea 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a21f2f1adb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 5e9e81ab1c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new bceef196e8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 30256ba474 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 64c4773692 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8e0a1623f0 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 6ebb1ce61a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new a0641cc7bf 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 2900c07578 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 84347b8516 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new f85584158c 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new caa8f947da 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 4a59e1974c 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 7ab0010bed 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new b4c94c8483 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 442ab9b23b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new d62e58aa00 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 58886d2bb7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 9217ccbe9a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 42cf793412 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ab85418dfe 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4eb0b1c0eb 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 20b6e02cf3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c4b37a0c30 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 5d5e7598b2 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 39caf0494d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 295973ed3d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 564551664d 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new a78a5256dc 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new e02ffa8847 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new ab5741ff26 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new bfbc37a620 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 0c14437201 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new e40906f897 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 93b3addf3e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new ac54fc9c2e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 89c149c3cc 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new ecfdb561c4 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new aee243da8e 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 59b029a595 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new c2fd62df77 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 711b357e09 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 1e3d76ded6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 33bd26494e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 463b724045 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 29281d9662 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 9b3f828664 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 42272445f6 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 3b1819abd8 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new a291fc4333 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new dcb826fc87 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 472b46cd12 407: onsuccess: #2661: 1: Success after gcc: 7 commits new a1490d5e7c 408: onsuccess: #2662: 1: Success after linux: 11 commits new d00b71f30a 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 5ab51ae012 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new cbd35434fa 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 4908de1b9b 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 74548bead9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 22a2194145 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 6ce28f2fc3 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new faa6cd7841 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 238052c299 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 36b4a452e3 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new ec0ffcc564 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 55317dd558 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 8596cca21a 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 92178fdcef 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new cd511c9336 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 1d68e04c0b 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 53c4aa595a 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...]

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 (eaf5d92c01) \ 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 1824 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31252 -> 31012 bytes 04-build_abe-stage1/console.log.xz | Bin 70896 -> 71328 bytes 06-build_abe-linux/console.log.xz | Bin 9160 -> 9132 bytes 07-build_abe-glibc/console.log.xz | Bin 244136 -> 243836 bytes 08-build_abe-stage2/console.log.xz | Bin 202684 -> 202752 bytes 09-build_abe-gdb/console.log.xz | Bin 38912 -> 38644 bytes 10-build_abe-qemu/console.log.xz | Bin 31632 -> 31936 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2932 -> 2688 bytes 13-check_regression/console.log.xz | Bin 7068 -> 7144 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 ----- 13-check_regression/mail-body.txt | 42 ++++++++++---------- 13-check_regression/results.compare | 9 ++++- 13-check_regression/results.compare2 | 67 ++++++++++---------------------- 13-check_regression/results.regressions | 30 -------------- 14-update_baseline/console.log | 64 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 ++++++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 44 ++++++++++----------- results | 30 -------------- sumfiles/g++.log.xz | Bin 3406076 -> 3402216 bytes sumfiles/gcc.log.xz | Bin 3030132 -> 3031604 bytes sumfiles/gcc.sum | 6 +-- sumfiles/gfortran.log.xz | Bin 1048116 -> 1041128 bytes sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217476 -> 217484 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439352 -> 438180 bytes sumfiles/libstdc++.sum | 24 +++++------- 42 files changed, 148 insertions(+), 245 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