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 75f347497c 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 90422b48dd 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards b3a7bf5867 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 881bf13938 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards ee8cadec87 427: onsuccess: #7: 1: Success after linux: 26 commits discards a5976466a0 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards b58df5b878 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 17acf94154 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 21b4fd0773 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards c179473537 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 0458cbb3c8 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 454678722b 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 1a1df12cbb 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 61c714f0d2 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 77603725ea 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards ae6b668688 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 2b78e1a308 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 80786d71e1 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 7d1b613867 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 5ec0140a37 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards fcc2d76c54 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards df7933fa38 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 5798decb4f 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 2c63e0176c 408: onsuccess: #2662: 1: Success after linux: 11 commits discards d3c2ff55ce 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 8caf664486 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards c7d0e1f048 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 602f32d817 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards c83669f960 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 2f16278b9a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards dc1dbf0927 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 865adde643 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 1e880470d8 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards ebbbd8ff1b 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 02744efbca 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards eaf62295fe 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards d08158d9dc 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 4770f4eed3 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 9fd0fb0cb3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 441d74ea2b 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 45546bf672 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards e1839f14bc 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 558289f5c5 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards e336ba73e2 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 7395fa9db8 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 50d5e14208 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 7e986ff7c9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 920af4b12c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards a0245e97b7 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards ba7b91c719 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards dde46698a4 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards ac54de5c83 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 8effcaa39e 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 58bfea29df 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards a63d65e979 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 70b01fd6e5 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 058d49fd04 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards a73d228a10 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 480d10c6ad 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards c05e1f38ad 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards ae4b707dcd 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards f9da731e4b 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 0693a5900d 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 474d8dbfc1 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 535fbeae27 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards b7e06fd9f7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 40e5dc7708 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 843f6521aa 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards d03452f5fb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 8cc6cf28d2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 7ea4f5eb76 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards c3136846b4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f4407db403 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards fbe25f11fd 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards af46ff8885 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 96baa3f195 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards e93ad14687 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards d6407058b9 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8c4ddef00f 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 50169cf0ea 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards a3402af528 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 7fd2aab835 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 45ee9cbbea 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards c0b94a32ba 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 9df0fac014 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 71dc120aea 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards c9fbb9b0ab 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 0e228a41fd 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards b35acb5225 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 39dacda774 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 03e8c0ccea 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 8812c4a049 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards b3fb7d6a35 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards b036c8d8d7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 32e4c94e53 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards d5de39cd96 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards d62311db1e 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 67dc2a6499 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards f3a459e435 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards dffda96d73 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 692acf5b93 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 83cfdc9f45 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new fe2be99ecc 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 500c21e552 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 9b591a8c3c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new ac70dc67e6 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new fd1f6b8e45 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 24efa76126 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new ed247b83ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new ab3d52df04 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new baa8ff78ab 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 998976f679 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 0597c1735f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new a8bc4f1db2 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 40e17c5345 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new cb64606778 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new f9de04b75b 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new ddabfae073 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 8c0d75cb4f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 88c6c1d0e6 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 4206e391bc 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 1d5a2ef2ee 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new d2e51fb382 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new e26d1da236 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 61eb573f46 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 4050e8bd03 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 62bf46c2a1 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 9a1f6e3c9e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new d1104ffea5 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ea982dd43f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 4418cb580d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8ec80cfe88 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new a9d2231a21 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new a58cf3a7fb 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new bb1f9c1b07 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 39e11d8a67 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 3ba529414a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 5cb71923ec 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new e33f175749 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 5d36e25e33 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 6317fb1b44 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new f70f85c26d 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 916f78a793 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 34c2bf2418 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 7659483901 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 755cc89b25 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 41f7d9c704 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new a693b88110 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 092de7159d 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new b560bb8f6b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 9c33f4d4aa 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new e5a4182125 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 07886e0546 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 979b6e802b 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 92d7e88064 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 74e0ec87fe 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 03bea870d3 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 595a551358 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new c7099c0fe7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new da66cd9cde 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new f0aa267872 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 404ddc756d 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new c6497a5b8b 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new d5b2a74b84 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new dd45ded5ee 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new c4fded6f01 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new e6ed4ea531 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 57b8ebba4c 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 3e6d5cefb6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new a88a74b6f4 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 69938bba8b 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new a1f3fab548 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 0cf628458a 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new d2c1f1f79e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new abbaa1f75f 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 0c70d8ed2a 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new dbecf334a2 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new ec0f5879b3 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 450b703ba8 408: onsuccess: #2662: 1: Success after linux: 11 commits new 66427323b5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 999ccf2507 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 4efbecda3a 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 71e5141ec7 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 03a5dd0a9a 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new a5372b1a44 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new b222dffdeb 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 2c9e6375c6 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 65af398287 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new a29faa8cea 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 50b18e17b3 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 37e8e2c4f5 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 4103a47709 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new b2233bce87 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new b90d409f54 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 403ef6b233 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 1a445279c3 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 58117192a5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new f2ee15bdf7 427: onsuccess: #7: 1: Success after linux: 26 commits new d2efce69c9 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 80e00ecf1e 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 03d44b5d55 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 1002e189f7 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 473e6169a5 432: onsuccess: #12: 1: Success after binutils/gcc/linux/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 (75f347497c) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2828 bytes 03-build_abe-binutils/console.log.xz | Bin 31700 -> 31028 bytes 04-build_abe-stage1/console.log.xz | Bin 71716 -> 72120 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 243264 -> 243956 bytes 08-build_abe-stage2/console.log.xz | Bin 201792 -> 202644 bytes 09-build_abe-gdb/console.log.xz | Bin 39240 -> 38972 bytes 10-build_abe-qemu/console.log.xz | Bin 32816 -> 32660 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3836 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3136 -> 3468 bytes 13-check_regression/console.log.xz | Bin 30324 -> 7860 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 30 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 6167 +------------------------------ 13-check_regression/results.regressions | 50 - 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 50 - sumfiles/g++.log.xz | Bin 3388172 -> 3394644 bytes sumfiles/g++.sum | 60 +- sumfiles/gcc.log.xz | Bin 3026876 -> 2998656 bytes sumfiles/gcc.sum | 94 +- sumfiles/gfortran.log.xz | Bin 1035916 -> 1039120 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217324 -> 217512 bytes sumfiles/libgomp.sum | 11 +- sumfiles/libitm.log.xz | Bin 2676 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423176 -> 437088 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 401 insertions(+), 6311 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