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 1a61252ddf 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards e836d02257 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 67580158e3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 2db4f38fb9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 67d61dd83e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 3fbcb402c8 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards f3e14d0fac 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards abee1ead44 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards f9eda1bbe8 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 1fef4c1692 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 5ae52eb2c4 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards c087123645 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e7d06d633f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards f9b9f0de14 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 2905fcde50 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 361b3829f2 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 2eb9356e44 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 4108dba0e4 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 0d5ee9e976 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 256326448a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 65751d199f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 89893c9703 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4250d933c5 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c13769841d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1445bbeede 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8b4fe6984e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 197f766ac4 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards ee68a9a529 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 189a95630c 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards a8e18ece97 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d3b1f18fd3 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards e33610f963 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 58d962fc54 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards e6fd9010b2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards e460046aad 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ac9607b4bf 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards c745de2a74 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 12990eee65 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards e8966d0ca4 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 216c1d17d3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3054b18efe 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 85b2756ec8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards bbc87a270c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 99fdde4874 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards aca293791f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 45335cc38f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 534eb32842 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 1519dd9214 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 57a168e578 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 97c7304619 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards c1bfc1655a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4e734522b4 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards cd839d4601 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 36037d4b06 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards b1f68222f0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 9d00ce00fa 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 8e7e864e70 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 4836cfdf58 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5bd7a3d2ce 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a9f8fc774f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards fabb8ce0e4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 10ddf2bdcf 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 35dde61742 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 768b19e316 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 11de4b8713 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2eab26184a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards b004b88798 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 4ca4a41817 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1bc11bd03a 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards bd7bd372c5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 788df3d946 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 09c905425f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 0d80d9a39e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 748ca26462 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards c080b66eeb 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards fd03e6e2de 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 6bc4481d82 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 1365d6703a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 18c8a06004 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards ad3e6cb06c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 194ae5da65 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 5665fc0986 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e7c7c96ae1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards bd95fef22f 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 9552c492bf 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards db27685c53 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 44852a0a0d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 5f35da33bf 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 1bf94bd7ee 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 2e219d1d39 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards dbfffd5da6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3b757f6d12 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ccfacbbf36 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards d3de0fce29 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards b8b1a55430 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 020c966194 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards a28351acb1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 27ff38495b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 07db0bd9cd 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 4615b3d1b7 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 4a2d125e5f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 6d83607a54 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 66bf3857fb 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 7da139a378 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 6fc5bd9bba 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ef30df4251 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new c6549e849d 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 4651f65d75 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9fce70bd42 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 41b50d2032 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3e6e9785d7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 4296e9b735 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 2b05806f57 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new f5c5a9f40a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new ed9672dc33 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 7c0ae9d4f7 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d0bf689893 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 9cb82aa629 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 45a13c64a7 295: onsuccess: #2545: 1: Success after linux: 10 commits new 95ebf0c98e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 950245be25 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new b2ccb93b11 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 179a9a1056 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 23412d8233 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new f4471e4327 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 6c1d2a8422 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5f7d3b762c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new f2b26377af 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 7a79026b41 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new f20b8b8735 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 16da28f9b6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new befda919be 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 55d3a1711b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 8e7f0a6233 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 73b37d8c72 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new d1cdcde4ff 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new cc56f30469 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7b52b01b20 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 771b764745 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 9d8204675c 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new e2af9c6838 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new cf27fda2f8 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new b90e8ed774 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ce8884f15c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 126158ca12 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 1f3cc430ef 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 9a17637e9d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 458ae02b37 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9c5c8b8650 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new bc9d890149 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 39ad255817 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 95d7e2f290 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new c0223cf115 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new fa48e9e070 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 189fee0e2b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ef6a20c04d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new e6e6b7f833 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 689b877827 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new a7e47dd526 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 20133d70c6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 30745a0276 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new eb38550b16 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 5348f008a1 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 6ddd585bc2 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 402749baca 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new f4109b9507 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ac62edb17b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 5212921009 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6e9300e2b9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 168b21aea4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 295307e4f6 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5407f29f08 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 7be837a5c9 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 88ff27f397 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 56f043820a 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 9b29b6e92d 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 384c3150e1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 1bff27b422 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 676826c8c3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new f23fed92c6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new a222b4a3af 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new c757ce6b1b 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new da43dda343 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 6ee0875fc9 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8e7e18f330 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 74c3f8156d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4e4474919e 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new cdc36108e6 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new e4660a4a47 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new b7635702fd 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 2cad31049c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3d8d209222 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 9fd8b28b98 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 89952f3086 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 0140d6d5db 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 6ee5423e97 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 9e04c1dfc6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new afe9446b51 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 825a156de5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 6e1403ebd2 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new a3b49d136e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 6dc6f1ceb3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c5d81031a0 379: onsuccess: #2630: 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 (1a61252ddf) \ 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 2044 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31764 -> 32172 bytes 04-build_abe-stage1/console.log.xz | Bin 73820 -> 74176 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 245436 -> 245488 bytes 08-build_abe-stage2/console.log.xz | Bin 205372 -> 208484 bytes 09-build_abe-gdb/console.log.xz | Bin 39064 -> 39408 bytes 10-build_abe-qemu/console.log.xz | Bin 31204 -> 31544 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3120 bytes 13-check_regression/console.log.xz | Bin 9188 -> 8292 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 46 + 13-check_regression/mail-body.txt | 94 +- 13-check_regression/results.compare | 78 +- 13-check_regression/results.compare2 | 684 +--- 13-check_regression/results.regressions | 66 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 96 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 66 + sumfiles/g++.log.xz | Bin 3399304 -> 3392096 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3019400 -> 3023272 bytes sumfiles/gcc.sum | 5289 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034416 -> 1033676 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217648 -> 217688 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427404 -> 432660 bytes sumfiles/libstdc++.sum | 160 +- 44 files changed, 3317 insertions(+), 3449 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