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 a1d1c03a8d 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 43dd46ae8b 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards dc78c7006c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 52915af2e2 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 037c4ee187 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 7027ecfffc 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards bd68a8d952 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards f2305c8c17 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 46e270190c 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e8e7af69a4 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards b9df3d34ec 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 41cd12d9db 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 51fedb95da 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 7eead10c87 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards f8255a4ad0 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 8070271ca1 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 4abd846de8 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 4328d3de84 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 9e0619ed00 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 34893c1eb2 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards c3da0716a8 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 8e7ea0086a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards d063878bc5 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 4b966e8a6e 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 33bc477487 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards de5561584e 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 4afe3e4df2 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 1530e64968 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards cd02752b04 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards e8e3d12c7c 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards c51f73bfbd 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 162793a9a9 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 08d75780b6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards cf8dc2fdc7 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 51e592a1de 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d3384be5cf 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards b1afaa51bc 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards cabd4ec729 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 9a1db11082 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 389685f786 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards c1567d648e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards fe1f0af1aa 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 2cf982ca03 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards dd8fb22cee 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 3023359d7a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards e53a35de2f 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 6f5bb33f68 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards ec68d4aa26 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards ee6d6af68f 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f2c3cb560c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 621e170830 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 174d84ac91 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards ed9e14f66c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 0c44b2f2d4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards ec47218423 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 11a9c5bd91 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards a15c7657df 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards fa31834a95 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 0a6fce67cd 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 07668ff67b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 237f0a7a4a 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 16b0346016 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 8aba5f8e62 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 537b79de59 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f7fa80efba 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 06537ed2f8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 21a36d4c26 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 5c24bd344c 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 225516c605 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 17cfa4861e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 2bca2784c6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 91bba3ed55 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 1a24c4989f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards ff3b1abf36 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 5beb9cce7b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 95a59120c6 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards d66c50655f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e21f39bacc 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards c7648a7546 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 3d648ee00f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 05ec7a45de 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 2dc5a36fd6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 93b0698a01 295: onsuccess: #2545: 1: Success after linux: 10 commits discards bd7e6a3db0 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 98503fa400 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards ff7c14b660 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards e7684ab276 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7846c76960 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 2caa65044d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 93541e78fe 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3b0511e3ce 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards fb945b285b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 8f5c25180c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 8a17f3dd07 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 8be07d7e36 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 78c6b0b1f1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards b7a5f1ad80 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 957010bfb9 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 8490e8fef4 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 77cafdd571 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 9e8a81c8bb 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c82cd255a3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 4a2d125e5f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 4615b3d1b7 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 07db0bd9cd 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 27ff38495b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new a28351acb1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 020c966194 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new b8b1a55430 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new d3de0fce29 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new ccfacbbf36 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3b757f6d12 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new dbfffd5da6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 2e219d1d39 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 1bf94bd7ee 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 5f35da33bf 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 44852a0a0d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new db27685c53 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 9552c492bf 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new bd95fef22f 295: onsuccess: #2545: 1: Success after linux: 10 commits new e7c7c96ae1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 5665fc0986 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 194ae5da65 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ad3e6cb06c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 18c8a06004 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 1365d6703a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 6bc4481d82 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new fd03e6e2de 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new c080b66eeb 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 748ca26462 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 0d80d9a39e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 09c905425f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 788df3d946 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new bd7bd372c5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 1bc11bd03a 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 4ca4a41817 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new b004b88798 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2eab26184a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 11de4b8713 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 768b19e316 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 35dde61742 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 10ddf2bdcf 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new fabb8ce0e4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a9f8fc774f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5bd7a3d2ce 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 4836cfdf58 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 8e7e864e70 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 9d00ce00fa 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new b1f68222f0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 36037d4b06 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new cd839d4601 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 4e734522b4 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new c1bfc1655a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 97c7304619 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 57a168e578 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 1519dd9214 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 534eb32842 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 45335cc38f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new aca293791f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 99fdde4874 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new bbc87a270c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 85b2756ec8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 3054b18efe 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 216c1d17d3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new e8966d0ca4 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 12990eee65 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new c745de2a74 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ac9607b4bf 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new e460046aad 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new e6fd9010b2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 58d962fc54 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new e33610f963 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new d3b1f18fd3 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new a8e18ece97 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 189a95630c 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new ee68a9a529 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 197f766ac4 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8b4fe6984e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 1445bbeede 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new c13769841d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 4250d933c5 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 89893c9703 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 65751d199f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 256326448a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 0d5ee9e976 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 4108dba0e4 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 2eb9356e44 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 361b3829f2 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 2905fcde50 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new f9b9f0de14 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new e7d06d633f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new c087123645 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 5ae52eb2c4 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 1fef4c1692 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new f9eda1bbe8 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new abee1ead44 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new f3e14d0fac 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 3fbcb402c8 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 67d61dd83e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 2db4f38fb9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 67580158e3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new e836d02257 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 1a61252ddf 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/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 (a1d1c03a8d) \ 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 1808 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31016 -> 31764 bytes 04-build_abe-stage1/console.log.xz | Bin 72916 -> 73820 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 244648 -> 245436 bytes 08-build_abe-stage2/console.log.xz | Bin 203924 -> 205372 bytes 09-build_abe-gdb/console.log.xz | Bin 38392 -> 39064 bytes 10-build_abe-qemu/console.log.xz | Bin 31840 -> 31204 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2652 -> 3148 bytes 13-check_regression/console.log.xz | Bin 5620 -> 9188 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 8 - 13-check_regression/mail-body.txt | 56 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 603 ++++- 13-check_regression/results.regressions | 28 - 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 | 58 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 28 - sumfiles/g++.log.xz | Bin 3391576 -> 3399304 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 3021632 -> 3019400 bytes sumfiles/gcc.sum | 3922 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038232 -> 1034416 bytes sumfiles/gfortran.sum | 17 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214952 -> 217648 bytes sumfiles/libgomp.sum | 442 +++- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433696 -> 427404 bytes sumfiles/libstdc++.sum | 42 +- 44 files changed, 3201 insertions(+), 2270 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