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 d9393fd5a6 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b89846a51e 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 7d01797fe4 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 408f4d978a 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards d348251507 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards f69b4f9afc 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 83faa3287b 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 1a88ae4a78 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 9207bf2e10 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards ed735ba84c 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 0cb78d59d2 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards d101983982 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards b0ba5b81a7 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 7616b46348 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 0d043194dc 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards ab254c7ae1 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 1e5910a8ee 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 4e978b81d1 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards e6ecd3fb5a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 238cf5ea02 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards ffc9d743d2 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 7c1d8a3eee 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards b0db6dd9f9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 9015a03360 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards f839ee4073 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards d25fae019b 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 7ec60414de 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 53bb1875e9 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 7714e1fbf1 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 06bba9b59f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 07479fb00e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards eab9133131 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards f4aaf58d43 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards c610c6cbab 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 77a07eda7f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 7a34aff2fa 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards a3237481d3 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards a784de5623 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 0980a17a53 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 37c7952159 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 57f599e341 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 77cd57896f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 0a0b572678 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 696f0b491a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 390f55dd78 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 4ba6995942 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 1849633438 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 2621c5f6b4 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 683b94ea1b 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 01c42e0d54 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 5ebb63597e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards afcbd9412b 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 7cd413c9fa 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 850fa35596 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 03f8d1e212 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 8ed7d78901 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 38e3ca5900 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 44fd02d617 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 8300fdd0d9 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 152c832cf2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 936b15a194 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 36387b1380 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards b0ffe15e56 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 20b131be91 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards d5856351aa 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards f8c3beff30 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 763512c3ab 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards dd51ed5746 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 1e2629106f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 5660850f39 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 35d846cecf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 3817d71b09 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 503266f1c7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 54fd19154a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 90c12ba3da 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards e7e61316f1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards bdb7090beb 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 9964649566 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 703e545a89 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 941e28bae8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 93b13c52c8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 393be1347c 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 954bdfa55c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards cfaa72e4ed 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards dcc0652a29 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards c2e8e36002 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6e33869bfc 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 64de7fd0c2 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 3334ab4b1c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards f9067477b2 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 1dcf95ec62 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 4b11f260a1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 60dfcad5b7 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 60fbdb5d6a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 4994bd79f9 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards e6bdd84595 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards c27ff240bb 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 336507aca6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards f2a103bb8c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards fa20d03c94 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards cfbd68f127 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 758bc6fdd4 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new d2c034f409 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 05dd1062a5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 4993d7aaf8 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 4b65b67241 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1c2d0d4a65 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new c71a934b49 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new a876543892 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 595c107bbd 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 92c5e3b61a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a676957b98 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 905f796ab1 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 49e75a728b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 86ee04c40a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 0c193fb207 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new a5f6c5c1ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new beb4089bc7 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 5f5a304541 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new ef31a9b070 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d873519e95 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ed507a208b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 7235436031 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 89367df106 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 099007a9b4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new ea6fabfefa 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new bb610a1f09 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 33e40cb636 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 29c7b95497 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e72a555308 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 7347586982 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 04b7024ebd 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 473c67bfb1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 9f304afc8b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new d476f4a3e4 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 4c2eccc105 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 9567f08645 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 7acf127e2d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 3856a8e7ac 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c8a665a915 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ac21cca516 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 8953053f80 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 0ddffe83f2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 517b5cd6b1 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 675d2a61a7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 0ecfd45b53 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 64cca71f2d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new b859501f12 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 902cc19755 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 57b0247659 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 85c602c3e6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 2a238246af 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new bf487234ba 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 80843f45d2 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new d316a7d759 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new fef79c2c36 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 6ede603199 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new d0dbc12a4b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 3308f07aab 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 6c87cfdacc 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new abc59c80a6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 3be70da5a5 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 5ae1da5cbe 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new e2e6513cf9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new aaab044c28 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new c1ff721d39 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new cf00408ee9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 2f8a7496ef 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 8f9a7a8984 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new a3ba80d54f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 562fcaaa39 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 8a97e7b49c 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 4e27ae47af 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new bd83c69dc5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new c71d75da3c 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new c347bd46df 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new efffec22ef 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new a13594a931 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new dafb13f4bd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new f5906f2efe 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new ce734434b7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new edb0ee109e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new cc2e9e56df 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 3611527d2d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 58dcf35e66 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 5ae3d1b0b2 407: onsuccess: #2661: 1: Success after gcc: 7 commits new f9f691ca8a 408: onsuccess: #2662: 1: Success after linux: 11 commits new d25bd4573e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new b099ae732d 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new d3b10dc187 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 4b64979b61 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new d877be6fe9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 4b0451777e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new a3519c9ddd 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new ca8616db95 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 4091937df0 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new fdda783563 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new f7e59e4759 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 7c753db49d 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 615b4f3dcf 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 30ab3aa84a 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new d766cec4c3 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new eaf5d92c01 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...]

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 (d9393fd5a6) \ 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 1812 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31100 -> 31252 bytes 04-build_abe-stage1/console.log.xz | Bin 71056 -> 70896 bytes 06-build_abe-linux/console.log.xz | Bin 9180 -> 9160 bytes 07-build_abe-glibc/console.log.xz | Bin 243964 -> 244136 bytes 08-build_abe-stage2/console.log.xz | Bin 202180 -> 202684 bytes 09-build_abe-gdb/console.log.xz | Bin 38644 -> 38912 bytes 10-build_abe-qemu/console.log.xz | Bin 31772 -> 31632 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 2932 bytes 13-check_regression/console.log.xz | Bin 8204 -> 7068 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 +++ 13-check_regression/mail-body.txt | 67 +++++++---------- 13-check_regression/results.compare | 51 ++++--------- 13-check_regression/results.compare2 | 129 +++++++++----------------------- 13-check_regression/results.regressions | 30 ++++++++ 14-update_baseline/console.log | 62 +++++++-------- 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 | 69 +++++++---------- mail/mail-subject.txt | 2 +- manifest.sh | 40 +++++----- results | 30 ++++++++ sumfiles/g++.log.xz | Bin 3422708 -> 3406076 bytes sumfiles/gcc.log.xz | Bin 3020620 -> 3030132 bytes sumfiles/gcc.sum | 6 +- sumfiles/gfortran.log.xz | Bin 1044040 -> 1048116 bytes sumfiles/libatomic.log.xz | Bin 2312 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217388 -> 217476 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434196 -> 439352 bytes sumfiles/libstdc++.sum | 36 ++++++--- 41 files changed, 261 insertions(+), 290 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions