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 14527c8a91 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards c522f49c7a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 59cd4129e5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards af442b3d5b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 50f655b291 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 0ee47d13db 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards aaf6e78de3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 0337abbeb7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 3b043585f6 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 58c3a2d8e7 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards d17650f8ad 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 8008eddd2f 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards c86b273b27 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards dd85c607c3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 7f78e5b843 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards d8be2ed61d 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards c4dda4a3af 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 0ec84c9521 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 9aed45e40e 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 7c5f1ee49f 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards ae0b586ffa 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards bd40f5457b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards bd9dd78961 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 7277a804e3 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 66082b2a12 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 4d5134a826 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards c03b738489 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards d45dd3da24 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 7a19add44e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 39bd4e3ee1 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ca14afee53 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 569dc206b5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards a07aae8da9 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards d5e30f6e74 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards bf85c26acf 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 3049678c13 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8e07bd6bca 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards b8e7a964e4 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards f799bff0c3 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 4d397e48ff 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards ea335e27a8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 81d29612f1 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 7adaef3cd2 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards c7aea57e16 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards b9c1ffa4f1 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 43a9723a06 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards f633d6d01b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 80d115ae69 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 629369e253 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards c3dc250a9b 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 692fca0f5f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 6f4f4c22bc 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 1f6358a56c 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 590e8a90f3 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards b1c38869bf 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards bdaba92875 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 4cc5c11983 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b12ced06c4 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards de644cbd54 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 0eef171cbd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 404a1ce3f6 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1bf7501c71 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 7b3a6613ef 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 1420032b11 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 5fc5ac7efd 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 5c9631f02b 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards fb4bf2cfb8 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 18762ac3c5 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 04a00c001e 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b770b67243 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 6be52e9138 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 961bcb3b49 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 01a8eb4f6e 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 34aec20943 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards b19b684638 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards f0044326c1 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 0d91e5cd9e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards d4936d1899 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 8ca2554da3 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards a0847c1ee2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards af92abead7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 9370cc47bb 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 1c3f95e3d7 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards d40edbdc46 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 783672b473 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 45348aec1a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 66f16d3e43 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 5831dfa902 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards bc0a23758f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 8a0e90845b 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 9361dfd7ba 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 408e5bbdd3 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 6ab3b4d853 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 996409fa3c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards d4bee25d28 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 37bdd81310 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 474268a71f 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 1e4aa3c206 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards cc7845bb7b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7eb3c4113d 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards beaf509497 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 24a519f33d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new e4fb9e024a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 6fc1fe9e4c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 6eb41c4755 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 687ea7e20b 293: onsuccess: #2542: 1: Success after gcc: 5 commits new f8878659ba 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new f9371893fc 295: onsuccess: #2545: 1: Success after linux: 10 commits new 2ed618cb48 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 85c772a7ba 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new e9693a0193 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 4026ba45fc 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 17f19e621a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 057cb57606 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 105fca6fa1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 4ea69b3b68 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new cf24cecbf8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new f2fe4c75de 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 962450a72f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 91b32de386 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 9710536338 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4e18e816fc 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 19b0547edd 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new def0cfa9ec 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 737fdf4b04 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new fffc229a82 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 9746ffee18 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new f2cfd16da0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 25e4a27362 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 2a6fdbba48 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 73883025bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 1717b43363 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 87fb7a44dc 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 3d0b591266 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new b8d3b6d159 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b48b6802a7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 8d258b8ca1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 1185ccc3dc 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new cec431ec20 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 7800ba34fd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0ba167704d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 8abbcadfd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new d68f8df3b5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 348e263362 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new c96f993569 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 03cdd40692 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new c8b8ae8401 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new e3a3751e11 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new a4d0f846ce 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 1f905d84b4 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 0df4348ac7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new cbee9ef73f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 3317c14c2c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new f999cfbc45 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new ee89b87926 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 63633cf31e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new c3c6252ffb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 057623b500 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new efc17692ee 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new cb005eb599 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 74feec7ba4 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 79a62997d8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new dc56f9f29b 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 4de93a6d69 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a87fe70aba 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 9e2b4656b2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new c77ea37082 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 21009cf8b4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a2ea60cf5e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 03a2589a9c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new e1ac0eb9d8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 705c5c21fd 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new fd470b192f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 00d8b6842d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ea9f7e7e25 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 1be5cd37f7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new d525cc7d41 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new a2c9394770 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new e9a8ff4f33 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 649baf8795 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new d879e4321e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 9f93a0460a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 748e80234a 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 7341cd9e1f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 39ff382a69 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 6b566bea71 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 2218cab0f2 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new b958ab9074 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new b891fe0192 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 7ae3487672 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new d86580a233 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new b43ecc74e0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new b83141a39a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 4fd2ec7c9d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 4aa7952666 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 06e91e9191 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 87e09a134b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 328c9499b9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 826653ccb0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new eac8217f48 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new d6456dc78d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 799d97e32f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 8ada807f87 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 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 (14527c8a91) \ 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 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31356 -> 31208 bytes 04-build_abe-stage1/console.log.xz | Bin 73284 -> 72960 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 245312 -> 244424 bytes 08-build_abe-stage2/console.log.xz | Bin 205188 -> 204296 bytes 09-build_abe-gdb/console.log.xz | Bin 38564 -> 38712 bytes 10-build_abe-qemu/console.log.xz | Bin 31952 -> 31516 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2720 -> 2796 bytes 13-check_regression/console.log.xz | Bin 6108 -> 5900 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 23 + 13-check_regression/mail-body.txt | 43 + 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 45 +- 13-check_regression/results.regressions | 43 + 14-update_baseline/console.log | 60 +- 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 | 45 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 43 + sumfiles/g++.log.xz | Bin 3406360 -> 3394120 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3000052 -> 3018372 bytes sumfiles/gcc.sum | 4232 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033440 -> 1035412 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217448 -> 217596 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435264 -> 436124 bytes sumfiles/libstdc++.sum | 50 +- 42 files changed, 2484 insertions(+), 2238 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