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-arm in repository toolchain/ci/base-artifacts.

discards dcb7c7096d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 647f6622b3 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 9da717b574 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 48f137eb70 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards cad056b783 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1a5d911b65 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 6ca3a65fa7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7602295ca8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ca0d24e2cd 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards a9f5237da3 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards d87eecd024 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 9b59059d9e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 416ef5785a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6c76e8db5d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards bdb4e0d536 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards deeace1ea0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards c01210a35b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 349a68f21f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ab5b0c0c73 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7701a38b8b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 4f35db6e07 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 6a702ec231 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 49219ff2c4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 06cfeba985 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0bcb2cd065 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards cad5a524f0 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 887f0b0df4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards bd177d18eb 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards f5cec54a2a 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 6d3637d6e7 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 4a2dbbd466 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 735e924827 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 9c982446cf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 549657ddd2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c07d520d7f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 137e0c9870 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 15b167b5fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards fc29b8a42d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 1a73a8b6d4 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 94977fefa4 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards c08d998088 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 251e4f8689 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards cab2ec0531 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards ac23fa4398 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards bf014e899f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards ec7ee63927 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f198f254be 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 363bcdc39f 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 070e5eb4cf 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 00731ad083 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 515aa4ff32 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards cb4cc2b8b4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 4e5b55573e 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards b1cb93bb2a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards b5ad702565 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 6112a8d020 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 2d80ae05f2 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 26b94625f7 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 4bac395ee2 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 1bdc9ae16b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 383dd10d6a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 74b22aac2c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 2a8e1e0411 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b8f86e7f04 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards f250a315ff 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards f40b2b5a8a 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 74a94122b3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 04d91d632e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 52365fa3c4 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards eb5a3c02a5 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f44459e6a3 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 8cd6cceb54 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 96a99440e1 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards fcdd513027 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 58143e45df 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 384b2f2b94 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7579277b79 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 65565fc2e7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards f3c7324896 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards c152160527 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 588ad90035 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards f90e22adb5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards d3b8892f59 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards a94672440b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 43c27b9a9b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards c02e1cd64e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 1b83abe4df 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 0f87ba29bc 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 79398e4f13 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 2cd68343a6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards e4dab25e6b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards b27b53b0ed 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 9f35d9a7a5 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d4bd30c650 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards c9a70cc790 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 54e3d6674d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards b3f559dbdc 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards a26c003613 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards f40305fdb8 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0ed05debd2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards eb0a842943 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 65df54c52f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 631459d4ed 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new bddff4a042 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 1de0f40efe 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 5871ed8d08 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 79bb62328d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 39ed6dc79b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new fc401a7d21 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 4c3d17947b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new c9f1ff5cac 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2c2b95f459 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 8f6fb11d48 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 77d0a93925 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 148f948052 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e5c1f05a7e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 3edc305c15 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 62f5675995 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new d2bd30972d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new bcf473f6f0 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 2903ac2a49 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 9d7c42837d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new e1bdc8c3c5 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 979abd611a 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 0961e8c8d4 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 8c1c5a87a7 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a6494db78b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new e4264467db 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 7ae9a96594 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 17f0b39aee 287: onsuccess: #2103: 1: Success after gcc: 9 commits new abf335f8e2 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 033824a05f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 8c379538f4 290: onsuccess: #2106: 1: Success after gcc: 2 commits new fd503c288c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 53a79c548e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 6b37ac610c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 434595a379 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 0ab2cfd49b 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 11a567e903 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new c76a8d6380 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 23f6cddec9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ceb09de022 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 0a61b8bef1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6ae4649127 301: onsuccess: #2118: 1: Success after linux: 16 commits new c835eec30c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new ce6bbab01b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 205b3314e8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 0a8f7c0c57 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new efaad5d145 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 02f85a451b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f0c5861033 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new f70c209f5a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6f0440c2b9 310: onsuccess: #2129: 1: Success after binutils: 4 commits new a49e035aa6 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 04c213fb34 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new a38dfe4568 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 145678a3aa 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 86d06a3fcb 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 4971be5368 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6f8b86f896 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e80bbafb29 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6a95731006 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1e3b2c9417 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 62b0cd628f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 61e7420364 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 9a39bda479 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 93b526a28c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 7151bf96de 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 30136cea47 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new e4f8920487 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new ff89dffe81 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 47dbc20e2d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bb1ddf68b7 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2bd2d84c49 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c452d6ab5d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5543e3edd7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new adc90b4a2b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 329af198b1 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a30b2cd39d 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a985ba53d7 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 088e362488 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2ce81de3f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new b4ce71bb88 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new a9c99e5559 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new feee2aed1c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 8152277730 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new a50f2c95c9 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 2e918baefb 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0fe3072387 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 1d66ea12e7 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new d6f0662599 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 7cefa9b54d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 2e9ddbfda2 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 76a598e198 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 01df53e78b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 923fef0e23 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 8255fbc9d1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 09f4db3b9d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 601c2a2991 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b9f688a74f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 27d8c65251 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 4aabcd9a11 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 79ec3880fb 360: onsuccess: #2180: 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 (dcb7c7096d) \ 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 1792 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32196 -> 32664 bytes 04-build_abe-stage1/console.log.xz | Bin 92584 -> 93428 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8924 bytes 07-build_abe-glibc/console.log.xz | Bin 236968 -> 236892 bytes 08-build_abe-stage2/console.log.xz | Bin 229316 -> 229504 bytes 09-build_abe-gdb/console.log.xz | Bin 39220 -> 39380 bytes 10-build_abe-qemu/console.log.xz | Bin 31452 -> 31608 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2700 -> 2760 bytes 13-check_regression/console.log.xz | Bin 7140 -> 7384 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 55 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 115 +- 13-check_regression/results.regressions | 26 - 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 57 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 - sumfiles/g++.log.xz | Bin 2651380 -> 2687472 bytes sumfiles/g++.sum | 46 +- sumfiles/gcc.log.xz | Bin 2222884 -> 2213592 bytes sumfiles/gcc.sum | 2197 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 888796 -> 891808 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214224 -> 213904 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434720 -> 443708 bytes sumfiles/libstdc++.sum | 44 +- 44 files changed, 1335 insertions(+), 1401 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