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 3ba79d3113 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 26e9cfe7d1 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 5aa88475b7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 1af3f20256 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 61cd89b1e9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 2ed4c3a4b8 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards a48430f123 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 428ce3196c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4f426823b4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b8b3a163c4 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 97c9a6b693 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 30d75b1ba7 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards cfd31f2808 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 1d71d3d69c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b21e6feff4 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ce1b524a70 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards f9652ec8b6 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 30c5f4695f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e92a625fa7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 99716a928b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards e1905cc602 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 62f77b2519 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards d920dd06dc 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2d57cce308 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 0cd1ac6183 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards b499252ebc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards b2e2b416ea 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6513d1b470 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards b223798130 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 28a857e7a8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 50db1b0d2b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5cd2a979d9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 0f324655b7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 855a082849 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6c95789d5f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards acf8e4e5c9 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e09b8bdb72 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 9130349efa 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards a6975f6f06 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 4cbdda44a5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards af0f81c018 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b921f72bb4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 2524c23226 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0bc01d0eba 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 538484bac1 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 660409d9e3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards bc32f89780 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6218a7f212 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 1736deb25d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards ca0527f5ac 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 2c8fb32703 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 2d18464607 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 64bbac606e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f3ab0136b9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards ad778c5483 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3dfd61f4b9 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8f11681bd8 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 3d21c3f8ca 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 203d3fa6ad 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 17b9d540aa 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards bff2b65bee 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards b18318821a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ce4bd4ec87 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 5885aea221 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards d38a9321b2 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 1077371d72 301: onsuccess: #2118: 1: Success after linux: 16 commits discards f4afeba4f2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 63de68f92a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 67506bf48a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 3ec833bf7b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 94047d3994 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 9a7abc4bfd 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 7fc5a25818 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 0aa9c48c5c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 39c26abeaf 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards b3c33062e0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 580fe89a30 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 016aa88e34 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 9aa30ad3c0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 9ae96bf36e 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 843f0eb7b0 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 7b16ca6003 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 02b7c1ef39 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards d7bc5a9bcb 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards aac0d70e63 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 872b02f320 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards e5ecf893d6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 6f1387b18a 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards b0f8139206 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards c455319ddf 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards d2f86a3598 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards b1b5bee94e 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1d29aca61b 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards e3fc9b7514 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 5e10982039 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards c49da6b65a 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards d0d10bfd91 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards cc8d40f97d 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 036fb6a964 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards e969c496e0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 9b9716a52d 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 01d3ca2b41 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b99c1b4033 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 0da6731fbb 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new e875e4bd4c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new c52b3170f7 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 65dec79680 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new f3e0bb708e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new e1ad743584 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 87459c4178 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 7592858483 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 8abe9a50c3 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new d83da1df05 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new c4e0be8dd4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new e8a27c8b92 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 9ab86350e4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 144352ea2d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new a59b9f207a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 0117f1b6c0 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 81b6e76c14 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 8171a02c05 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new c38088b72c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new c31179c2fe 287: onsuccess: #2103: 1: Success after gcc: 9 commits new f2240c5be2 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 263c314052 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new a2f97580bc 290: onsuccess: #2106: 1: Success after gcc: 2 commits new b61cd5a655 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 055e96bece 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new dd136d6a2b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new b3d78d603e 294: onsuccess: #2110: 1: Success after gcc: 17 commits new c97fd8dee4 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 62dab02d95 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 91960f0d6b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new af8811b6cb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new eff8a93954 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new cf245368f2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 5316b55082 301: onsuccess: #2118: 1: Success after linux: 16 commits new 953e02609a 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7c42d8034b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 54fa6fb85c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 436b0a127e 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 558e5a8bc7 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 6c3c28c5c9 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 5e8e6279b6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 56385ffd96 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 9108e50d52 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3ceb6bfdba 311: onsuccess: #2130: 1: Success after gcc: 4 commits new f21cbb86e6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new dbf44b48a2 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a7af6c2dbd 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 8204652404 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 9de6ad7f2c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new e5bd8f9e5c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 106b8cd52a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 016b704fb8 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 5b0147c7ab 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 29e8cd68c7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 35d67d3559 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 87332a3fae 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 3eab5e328a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 27f73b6a2f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4846eb7be5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 1d563aaf76 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 51e5f0f5a3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 4cfc004e55 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5c10b33e46 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 891915d279 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 684e5b6e7e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 43f7ecf29d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 1a65a4adb8 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6533d6f684 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new e101c5b4ed 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 0c4af1df5d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f81f15244f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 5cccfc95e7 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new bf04cb79bd 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 50e169ce32 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 21e94162e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 9056ae58c5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 12d4542e3e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new c1cc0ba3c9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 62cf2b14c7 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e69b29d566 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b4d9d1b1e2 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 32794bee64 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new ee575c6a21 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a9ef5ed833 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new a9565436c3 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 35c096960e 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 635a4cb077 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 22f14fe993 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 0992c24eda 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new aeab30de29 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new c2af415fc0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 27c8e07aeb 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new f082e5f32f 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 5dafd9f2dc 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 771fe2d570 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 793c5fddca 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new cd46eaa96b 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e6b2c8f433 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 8dee47c368 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 5aa33b93f2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...]
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 (3ba79d3113) \ 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 1776 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31064 -> 30800 bytes 04-build_abe-stage1/console.log.xz | Bin 91904 -> 91424 bytes 06-build_abe-linux/console.log.xz | Bin 8884 -> 8884 bytes 07-build_abe-glibc/console.log.xz | Bin 236432 -> 236456 bytes 08-build_abe-stage2/console.log.xz | Bin 229072 -> 228088 bytes 09-build_abe-gdb/console.log.xz | Bin 38468 -> 38080 bytes 10-build_abe-qemu/console.log.xz | Bin 31256 -> 30864 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2840 bytes 13-check_regression/console.log.xz | Bin 17844 -> 6908 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 96 +- 13-check_regression/results.compare | 213 +-- 13-check_regression/results.compare2 | 3046 ++----------------------------- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 98 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 101 - sumfiles/g++.log.xz | Bin 2626216 -> 2639288 bytes sumfiles/g++.sum | 56 +- sumfiles/gcc.log.xz | Bin 2172180 -> 2179132 bytes sumfiles/gcc.sum | 2531 ++++++++++++------------- sumfiles/gfortran.log.xz | Bin 895704 -> 891520 bytes sumfiles/gfortran.sum | 15 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214044 -> 214100 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431832 -> 433712 bytes sumfiles/libstdc++.sum | 25 +- 42 files changed, 1593 insertions(+), 4786 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