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 202f4a6459 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 68e862c33e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards f56b4cdf8b 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 8cbda5ad50 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards f6ab7ca07d 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 36abd70b9d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 8928ea9fbf 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 84fae4c047 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards cfd355fead 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 913546624d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 34caf91d6c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards fb04beb76f 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 9734bc7940 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 69101e9480 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 93e34f0bbc 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 5c70102278 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards efff9a2147 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 86f1ded720 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 64517a249d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 6f46c99691 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 3c5174e9e8 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 007278768f 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 2f7f4bdb94 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 9e380eabc6 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards bdaba27326 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards da14a7ccec 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 2d4c3cf2b5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards ee33d10fdf 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards be564dac49 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 76734f3962 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 69f501cbcf 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards a3e85d4773 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 119559533c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 48dd8f2ed5 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards b06a071e67 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 54b294cd88 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 3ad48d6084 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards dadc9b3515 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards e160919b93 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 090667d07c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 533faaea22 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 18a5af8e0a 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 8ba11a2d96 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 1c470ed013 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 6b686324bb 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 639f68c725 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards d243f62c78 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d194c2ec4c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards ed42dffe38 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 505d98bb24 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards edc559d059 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d47e71754a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e23718dc41 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 9fc686effe 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 48ea558d81 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 1d17e4f3dc 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 99835ef19a 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e941a1f4e7 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 2f83e5bb56 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards bd7e887148 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards bc3b316d48 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 72a6de6f81 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 251663d8c0 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 470d7e70d2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 95029bf5d4 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards df133d8e21 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b6c94d9438 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 1e5cc062c1 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 8777e6d118 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 97207b2529 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 4a458be42d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 4f6e12428f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 6a2308efa3 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 60aa962c06 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards dba38031f9 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards ec50eb9686 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards d7430bb107 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards c8e865b5a7 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards f76141ae25 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 5959d9f913 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards f9146506e1 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 81de44137e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards e9d76e8339 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 090c7492d7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards e3fabe8ae3 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 9dccd679d6 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 2473baec22 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 504c41cd5c 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards b648c9c220 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 7552a72abf 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards dce6bc06ca 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d392c9058a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards cf786d0db3 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 86b8c03caa 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards e2abdab924 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c848eb8beb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 7c814e6958 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards c9dc1399a8 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 9822a725df 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards d883cfcb71 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 766a503b4d 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 4a4016140b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 200bb0041a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new a163cf4447 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 6698e3c78a 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 2e7cf1946c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c74dfb36b9 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 3a8912eac7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new c0d0aa2a75 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new e9ab679f46 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 8c95818b4b 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 81e0539551 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 501ef64768 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 6b29dfcb19 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 5a87c1e500 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 60037737cc 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new ceb3354b93 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new bf6529ce94 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 6ef468f55f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 3669d591e1 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 1945f13e6f 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 11abacdc69 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 4b7ae7efad 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 8e744d24e0 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 345084e80d 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new d02b9898eb 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 12b69eeb66 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 587ebbf80a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new c2fd3f1c9d 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new a5af06f24e 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 1afd7d4387 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 14e5253bb1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new e71d2efa64 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 2ec255feb4 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new c7c6f3f5f7 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 547a54daf2 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 28c267a62d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 9680e510fd 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 07ab171388 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new c7b13a3d3a 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 157b89f2a8 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 7b21e8c0d1 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new a0f9f0a547 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 094e48cf8e 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 7668fab8db 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new b081513368 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new bafcc231eb 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 7fa9989262 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new ee4889dd5e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new c3c17465f2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new c751031eae 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 4e5f89deed 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 280855bbfb 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 48731c4664 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 29efbf726d 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 84d9ac3ad9 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d7f9cdfdac 293: onsuccess: #2542: 1: Success after gcc: 5 commits new a96fcd2057 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 4512ddd5e3 295: onsuccess: #2545: 1: Success after linux: 10 commits new 80b9794e4f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new c60b113f6c 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 19de27adda 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 47ec4d7f4e 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new a180963915 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 7e9d71aa71 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new d4e37ee607 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 64747e660b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 0a56b10063 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 17d1ccd8ec 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3e98562169 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new de6bf54a33 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 56f4df2111 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 242e9ffcca 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 48e6356230 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 30b7711532 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 9a9f5b4394 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 0d56ff6781 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 2c24b754d5 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 458bee8aa1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new df2f0bedda 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 380c6825f4 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new c0afc884ca 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a786311f32 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 96424bf31e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 83093d31ba 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 9a98c3405e 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new ffbd594f0c 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 5ee3ed1d17 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new ab832309e5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 68c6f3fff2 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new e4504eadd9 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f7904ee271 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 089180930c 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new de4b861db0 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 0cbdd8f242 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 9a54c15f5d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 5c9144e83a 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 24dea51db5 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 7424101fa6 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new e4b9934bb0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new d87f8cf4eb 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e50fa69c6a 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new f53b8ddb15 339: onsuccess: #2589: 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 (202f4a6459) \ 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 1760 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31772 -> 32288 bytes 04-build_abe-stage1/console.log.xz | Bin 73912 -> 74128 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 247200 -> 245696 bytes 08-build_abe-stage2/console.log.xz | Bin 205684 -> 205596 bytes 09-build_abe-gdb/console.log.xz | Bin 39208 -> 39464 bytes 10-build_abe-qemu/console.log.xz | Bin 32920 -> 32600 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2888 -> 2716 bytes 13-check_regression/console.log.xz | Bin 7088 -> 6160 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 93 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 48 +- 13-check_regression/results.regressions | 44 - 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 95 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 44 - sumfiles/g++.log.xz | Bin 3423552 -> 3431876 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3042196 -> 3027244 bytes sumfiles/gcc.sum | 4646 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1041628 -> 1037452 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214756 -> 214656 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2704 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437604 -> 434080 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2476 insertions(+), 2710 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