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 31580f8a4a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards d2a3501833 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 816c0a1853 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards d3d3a522b2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 9b4efe2648 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards e0eb53e51d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards edf00440f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 94e9fcea9e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards bb93b0e255 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 84934f1745 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 7e57119117 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 710a3d3354 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards a0bd1d699c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 14bb8c8833 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards e70ac8f759 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 6b33afe3a4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a81db0e926 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 9dee344351 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ccae250b0a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 40f39aee9e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 9c5cf39d7f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards f07bc324be 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 58d3bec070 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards f8569f70ed 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 80a4cc5d42 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 52d3cec15b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 3a8545972e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 47455750d7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards cfa7060c12 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 165f5ea8dc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 31c5966e32 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 3671d086e8 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f0276ee534 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1c77504c4c 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards bb404da8b9 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 59c605f8a3 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a4dc09cae5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9381ea4671 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 384dface6c 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d29b439b94 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards d154600b12 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 63da53dcdd 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 14ad5af409 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 51ccc60b17 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 74942d1f6d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 7d58d931df 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 65834babc3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards f35d9b8d72 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0b7f076969 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 082d208c0a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 721a09ec7a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 7ee1837f90 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 345582d9c2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards d1f3638550 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 0a932b520a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards c6ce6ae42c 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards bac431bc78 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 6b85320fe8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 4f11ef3cf5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 9c3a5de508 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 7b9bdc3e20 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards aeeb0a2b6a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8be1cd72c0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 9b70cc34df 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards def6929902 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 5b9576a404 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cc58160ad2 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 2d0795c2bd 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards fd7caa0084 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 266b495a2d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5d19733f15 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 237f2656cf 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 6db582d983 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 0bacfb836e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards c4357f2ed2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 194ddba350 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 5fac55d7c0 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f7da10850b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 9028e63c45 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 355fea3f38 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0b11c6af9b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 85efb500f7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 30ef48cfd2 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 4ef8be6641 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards abc3d28d34 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 02864561cc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards e971ffc8ca 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 154bbf2a73 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1e253daf79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c5e69a95e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards c6fc858d6a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards f83d16a0d2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 6c73a73cf5 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 9c17eb74b0 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards e6d4995242 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 8c17a7c653 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0d24ee050d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 06f089a07d 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c197e7abc3 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 48f3c5f47c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7dc3eb6d7b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 718d478cde 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 4b3d1ade1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new cbfb22146b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 61212a68dc 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new a5b387aa32 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2c42d26e7a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new ba630b0cc4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 175c4c315c 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 11752753ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 374b949d7e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 5ad2b9f601 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9bb606ef46 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 52ab4914e7 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new d618834847 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 0bee63f8e4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 614f5914b8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 1210658edc 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c3d5879b7a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f5f4f7f7c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 6f6ec5be01 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 187cf237a7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cb4df6717c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1338f2dd2c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new eed0d8f73c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 425cac2810 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f27d5523e9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 4620013fe5 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 03967a8485 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ffa4534dae 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ef2ac39d8c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5050f53474 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 84857818a1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b7f739578b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d0c6a0a7b3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3cc197e27c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ad1e5646e8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 1f5be54c2c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new bd77d30b02 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new a128fd26fb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 818335068b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 426d8cce22 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 79d08b4d07 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d33dbd2b76 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0a1f4c2144 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f6e6477837 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 006bead909 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new c8589352e2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1e68a39d78 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6ee94b987c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 97c70e7c67 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1f141bcdba 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new fbb1efe8fd 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 20059e61b7 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 47e1fbc3de 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 4265a9c7b7 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new ea50967208 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e5c8984419 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 2ebfab827e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 50478702ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 902363c34e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 14dd815920 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 1b4214e123 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 9d9cd3a35e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c6226648d0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 068097d736 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new e623f2dcbf 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 39bc88570e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new bcf44f60c8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 5a78f4eba8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new bcf0b3811d 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new b1d4b1868a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4df578cca4 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 328c944d05 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new aa1760d3d9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new a81f791f20 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new ea1ba30b66 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new cef2cf9ca8 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new c9420a677a 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new bd89dc5a8b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 3d9578e9b5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 455eba624e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 91c05f2d82 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 0c1490f4bc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 7be09f720f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new adb1986a71 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 988b0ec240 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 3755c8c37b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new aa3f143a11 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 84a591e0c2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 40af0bab10 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 2e684fe1d4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 1f4f169c31 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 62ec704db0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8d1d7e3fbb 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 23b6789c06 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 963e42ce41 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new c43dd6a5d2 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 98e3d5df91 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new eecbdf7c2c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 7176015a5b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new ffe3343973 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 7a895be0f8 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...]
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 (31580f8a4a) \ 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 1800 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 31388 bytes 04-build_abe-stage1/console.log.xz | Bin 91424 -> 91608 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 236892 -> 236972 bytes 08-build_abe-stage2/console.log.xz | Bin 227612 -> 228768 bytes 09-build_abe-gdb/console.log.xz | Bin 38168 -> 38664 bytes 10-build_abe-qemu/console.log.xz | Bin 31108 -> 31928 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2640 -> 2812 bytes 13-check_regression/console.log.xz | Bin 6108 -> 5968 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 19 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- 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 | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 40 - sumfiles/g++.log.xz | Bin 2655284 -> 2641368 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2220492 -> 2202220 bytes sumfiles/gcc.sum | 2594 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895356 -> 891556 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216944 -> 216836 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443648 -> 438260 bytes sumfiles/libstdc++.sum | 30 +- 42 files changed, 1425 insertions(+), 1600 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