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 d10f9b38df 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 30d3faee89 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards be00d2772f 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards b35e657d36 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards c7929e818a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards dfb1504ba1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 291c4f7c2e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards b4b9768185 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e8ced3cae8 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8b95ac7b74 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 308178fe13 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 989152de25 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3e7cfee2ca 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 42cbe1597b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 2a1704f5d9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 173a417c69 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7e025224c7 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 145e588967 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 69f37d5da2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 75726eee03 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0b33db92e4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards bae9b98975 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 8879d845f6 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f843837349 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 23a9653db6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 3f0036490e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 30e98715d4 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 02f24bd0d0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 7cae67449c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards aa06529664 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 77bc296916 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 075688961b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3930a5f46e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0d28e2e29e 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f5de9f78ac 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 20c6cc8afa 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 9e939e4290 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 045bd3f208 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 463eff45ea 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7ca6603d94 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 5a8a7d362b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 0f7d98f22a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards c15f4158cc 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 3bcceddf9d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 0fc63d5965 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards dcf4b391c1 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6428c1ef18 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 0086b8ed91 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 88223687f5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards f426d23097 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 569595e342 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards d360428b7b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards be03c32fba 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 53719cd45f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 15d850accf 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ed9a524b16 301: onsuccess: #2118: 1: Success after linux: 16 commits discards b100233e08 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 939615e23d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards a277f40d90 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 4b874580f9 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 37d8531fd4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards fbeafd8f5d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 5ac5035593 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards f94fccc739 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 0d1bf1871f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards ff991b4cb6 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards a4dd2a310b 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f737d43236 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 40ce0776ce 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2d201d8e55 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards c2f5bb918d 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards a63161fc6e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards a849d15570 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 2af30d0864 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 37b98fe011 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards eb880c40fc 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards b9841c769f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 06db67a1f5 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a35b39c113 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards ccaeb3ec9f 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 95d2467d92 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2d0e118960 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 194c6b8135 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards a4d254dd86 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards b3fc3d6b96 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 0ea618aacc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 1feba647b6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 72be1fbac9 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 88b154db1e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 1647cdaee5 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d592c974e0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 832c658e13 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 190c786675 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 7d66e2076b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 6336490cc5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards e7e480cd35 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ca72861df3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards c50851331e 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 8590cc01d4 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 6d3ca238e1 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 36156dd843 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new c1ff6d4f86 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new fd960b4f27 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cea3433b52 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 1e09048354 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 145eec3e8e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 8e35155be1 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8c64f6a73f 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 52d68d9942 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new b4347fd24f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 2680cf7015 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 5bf3b8cdfb 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 350e653f5d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 01ee002f1e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new ff77288694 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new c4f194b8ce 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new f1d26d5bda 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 06b18ab60d 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new bffa0e848e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 78f985b6b5 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2c8c59e75d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 9574f27c6b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 02ae1a9245 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 22ddcf94d7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 4f50fa3115 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 8009d2d4f4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 435445f1b2 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new f025fdb98a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 3b5d10ded9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 148b817cce 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 9fa84d395e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 8c3aa9f6a3 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 90c5f030c0 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 12798a45db 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 5cae7cda4e 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new de73d89eab 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 3d5fbf86c0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 337ea23a0f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 5839e8ed3d 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 020b440d6c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new fa03461db7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 35cc1472a4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 726d8d4d00 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 15ecec403e 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 360b5436ca 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new fc20bad8f7 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 45d8edc0c6 301: onsuccess: #2118: 1: Success after linux: 16 commits new fc4414f8e5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 04b6e6ede2 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 5b07969f60 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 80defc3d27 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 5b1a210576 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c11a71649b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 12dcc36b38 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c87b00923c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 90868cd7ff 310: onsuccess: #2129: 1: Success after binutils: 4 commits new eec1af9e15 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 183c36c23c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f9dc6e735c 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 7fdd3ca6e7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6f04cd1193 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 0c85b7f929 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new deb45ce93c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 494ce86fa3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f0bf401f75 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 032f5fd234 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 04a3838b4f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 582ba1406d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new e4a4b4cb6a 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new e2459a1026 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 018bd2dc85 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f76f2aabc5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 3b68de234f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new ad922212ac 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 8356ca62d7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 77197bbe17 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ae249676d7 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6369b2185e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 3359bc65ed 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new aecb902e8c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e27f1105f2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new aad22b63b6 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 0cadbd4524 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c8e952dbf0 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 719bc3dac5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 82f6fc9a80 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 5b0cd4958c 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new ea6d004bee 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 013328890b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3d0efb8b66 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new afa20008d5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 6ff195c5af 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e3b03f7972 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 66816b67f9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 43aa0ffed4 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 3b10dd90ce 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d21f25df8c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 643545267c 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 72276f6ee1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 0e12df336b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a08eda2827 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 26eaa08510 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 38655a7740 357: onsuccess: #2177: 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 (d10f9b38df) \ 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 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31704 -> 32036 bytes 04-build_abe-stage1/console.log.xz | Bin 92864 -> 92584 bytes 06-build_abe-linux/console.log.xz | Bin 9008 -> 9152 bytes 07-build_abe-glibc/console.log.xz | Bin 236928 -> 237348 bytes 08-build_abe-stage2/console.log.xz | Bin 227876 -> 230600 bytes 09-build_abe-gdb/console.log.xz | Bin 39072 -> 39352 bytes 10-build_abe-qemu/console.log.xz | Bin 30868 -> 32316 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2908 bytes 13-check_regression/console.log.xz | Bin 18344 -> 7220 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 12 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 2077 +--------------------------- 13-check_regression/results.compare2 | 2260 +------------------------------ 13-check_regression/results.regressions | 101 -- 14-update_baseline/console.log | 66 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 101 -- sumfiles/g++.log.xz | Bin 2669620 -> 2674380 bytes sumfiles/g++.sum | 52 +- sumfiles/gcc.log.xz | Bin 2246516 -> 2245532 bytes sumfiles/gcc.sum | 2226 +++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 900272 -> 903128 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 214088 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444084 -> 441208 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 1320 insertions(+), 5740 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