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 ea738d2a93 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 0fc9dc8ed7 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a2d4bad3d0 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 5d584c13bc 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 6a86d78c04 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 47aaf59ac3 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 148fc8bcef 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards dff3e3feca 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 2644e1912e 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards a743a8f459 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards f083c6f626 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 27e78d06ff 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards a27c887749 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 3292a22ce0 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 20d6ea82f6 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 995978c090 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards b3959a1f07 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6f3930cd7d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 0f57208285 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards ee61dccec5 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 30425d9b35 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards d08ba51482 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 2c2a3c0954 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 2f59b4f2a5 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 6f45038e9b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards e2b8cac2f3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1a9fe3f8be 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 61e746ad93 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 8748ade8ae 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c8b9c95c11 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 6669a5a6df 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 9aec3e1364 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 9d99943dde 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 7b4cce7ecb 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards f1bf246262 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 14eb3c3924 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 1e9c44aafa 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 81959493d5 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 9e17abaf51 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 3214b76939 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards f52e90597a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards a2dc1c87cc 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards b67f27c7f9 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards fe661b2154 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 09aad6dfff 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards e3dac0d65f 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards db31b2677e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 0be39182da 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards f471e6a13f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 2555030de0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 6a241ffb2f 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 9d91b6649c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards c67dba8b10 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards a10fa69688 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 25d3044b1d 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards e2efe87c0b 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards d4c80729ad 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 78f43cf869 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards d6f8ebbbb1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 1f4d4d9414 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 18f70e334a 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards de9e79009c 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 3061eda837 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 2ff71dc41e 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 2f26b18548 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 76ddf078a8 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 289cede9db 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 1ee653d6b6 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards a48c58d997 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 95a664e2b9 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 31b35caaf6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 31475775d3 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 72fe4107f7 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e17e3ba169 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 832d15b1bb 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 0d0e4466fc 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 8c63abb911 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 98212c1108 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 490e895a45 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 57f579c6c3 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards f7c0d222a8 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 1035542938 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards f8ebae26fb 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 0b5980aa94 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 2ebf5c54ab 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 54cbd38b5d 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 78f1083969 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 14163b178b 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 9b4776c312 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards e796246424 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 69ee459fcd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 21251dd91d 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 59bd74ccc9 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 083aee318a 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 414128200d 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 134abdfffa 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 804ea0c92a 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards cb93e50f20 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 8e9cdb6a2d 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 863864d31d 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 9bd26059c5 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 6814ffae36 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new a4b3a66744 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new c8cc22556c 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 8887c52d69 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new a4f1051908 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 84d899387e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new b43ae544ec 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new b73a1de962 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 8835a85786 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new b3a677c737 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 3d5391fcc7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 2a0dec17ef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new ec05fb9df1 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new f26ed3d041 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 924166d38d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new c569c3893c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new f036fc1a27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 64bea2addd 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new da49f65f81 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new d1377f8049 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 7eb551071a 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 798f74eea2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new c9ee4c75bd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 9f024f73ac 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 801e40eb2a 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new c305a8d04c 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 4a8f88205f 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 50643c7fee 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 94f199e200 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new c2b1813ca2 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 13b63dbcc8 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 875d3ed856 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 4e5e5bbcc3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 592f68a44f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 6d44bf823f 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3369c65103 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new a96579e896 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new cb83f4864c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 71dd563004 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 50eef89c4f 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 1d06723eb8 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new c003fd3d2a 295: onsuccess: #2545: 1: Success after linux: 10 commits new 5e2cf6b022 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 4dc669cdf0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new a97dee738f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new b92b6de992 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 7dd8cef8a1 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new e494126d21 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 5f88f436d9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 6ecec43b8f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 62e5c030c2 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 80ac09f55f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 7661c1ee8f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 6a99279e18 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 61d7910fe0 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 80ca00abda 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 28c4788e76 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 3e1d714549 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new f11bf96a26 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2a1e6b30df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new fe8b11159c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 674387fdc4 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 0f290e6203 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new a450f0e7d2 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 97d34448b5 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 5ff2730124 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 0ef3c76de2 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new aaf6b9bab1 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 7d4b7938b8 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 89a0d5ab8d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 37adbcc3e4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3f15937f54 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 4837288ae9 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ab0304e77d 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f5952fa28d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new b749443807 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 36fbf5b75a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 0f682c6978 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 9c7a976fe1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a430551f18 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new a02943c885 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 5d1f11eacd 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 0f6520f907 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 3baee8453b 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 929f470ecc 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 241f19f9c6 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 8d959a5d43 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a5b726444a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d935089267 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 96a1913a88 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 208f7cd5d6 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new c567f0329a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 1e053b00ab 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new b34394542a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 68876698e9 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 2a94159467 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3968f2152e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 72aba17930 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 7872a29d69 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 4592443500 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new c953812402 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8ce9b13dbc 355: onsuccess: #2605: 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 (ea738d2a93) \ 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 1784 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32104 -> 31612 bytes 04-build_abe-stage1/console.log.xz | Bin 73428 -> 74280 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 246296 -> 245640 bytes 08-build_abe-stage2/console.log.xz | Bin 205748 -> 208484 bytes 09-build_abe-gdb/console.log.xz | Bin 39164 -> 39044 bytes 10-build_abe-qemu/console.log.xz | Bin 31724 -> 32200 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2968 bytes 13-check_regression/console.log.xz | Bin 11268 -> 10716 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 36 - 13-check_regression/mail-body.txt | 96 +- 13-check_regression/results.compare | 57 +- 13-check_regression/results.compare2 | 217 +- 13-check_regression/results.regressions | 76 - 14-update_baseline/console.log | 70 +- 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 | 98 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 76 - sumfiles/g++.log.xz | Bin 3413848 -> 3395872 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3022648 -> 3015216 bytes sumfiles/gcc.sum | 4116 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1040116 -> 1036084 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 197580 -> 214852 bytes sumfiles/libgomp.sum | 971 +++++++- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439552 -> 429400 bytes sumfiles/libstdc++.sum | 236 +- 43 files changed, 3262 insertions(+), 2928 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