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 232d98deab 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 9cb2abe2d2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 9e1695216e 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards abf3325c31 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 8aa60b6646 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards e3cb90096e 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 4a6b483752 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 53d57cd85b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 9cf208c89a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 6737423dad 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 74f431497d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards d984ad2de3 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 0ca678a514 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards ea0083b0af 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 6520bf04dc 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards b6f87c558c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b1b5e411a2 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 795eda0e1d 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 24303c9425 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 4bd8a1db60 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards b216b415c5 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 203f79ea16 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 1cda530fe6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards e6a5722431 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 9dda0d4d78 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 0a6027ba92 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards cb65633f61 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards ee4eaeacae 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 8b25fdbd52 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards c1d61e4714 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f9f591e4ce 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards fedccd3245 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 77c4fb184f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 6fe6220ce4 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b2397d9a15 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards d95c737a09 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 2113361b1f 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards f3a3da9f08 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards f870977342 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 7f47b69c4b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 0b3178fb85 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards da9399f035 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 1888cefbc0 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards b80ba16062 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 13aeeb2feb 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards af86305a49 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 2926d554dc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 0142ff4cb3 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 038f373baf 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 6703aa5b0f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 4f18aa3ae2 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards eb29b32692 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 1ec07ceafe 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 494f06b1e6 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 6a8992a57b 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards e32a5b964e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 54d9eec41c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ac9d108e2b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 946ede4015 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 20cda52381 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 0806f6446e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 79e534bbf7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9b76b4d963 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards f92757f0e8 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 39380334d6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 282707f72e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards b42d7cbb0e 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards e7eac36b5b 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 8fc5e00ead 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 132f614c04 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards d561ad71ff 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 11f2c1ef3d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 21eeba746a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 4bbd02cd41 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 8ed1a137a4 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 2283b47daa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ba12cb832e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fb07aee708 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b102d8c093 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 3e1e5754d8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards d2c6194a27 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 27571f476d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards fa41ba01f7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 95e23dd75b 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a6bb88e55f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 16f461f651 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a9e9da9e9b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 332dfc4959 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1d267483b4 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ba095a9fa7 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b289e31939 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3a0460554b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 1aab61e830 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards a2f1e45624 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 295dea88fb 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 21170a6483 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8945aef19e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 72864ee627 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 48bc6e7599 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 5f9458828d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e4f1d42654 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 2274632b22 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new a940669207 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new e337774987 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new a6de1b25e5 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cdf24946e6 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 7868d64665 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new df706fae42 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b2a62e0bd3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 64ef45a9b8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new dfbc0414ae 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 4ffe13ef64 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 9750bcadf1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new dc88c27dce 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 563583a4e0 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a1e25963e1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5223086ea6 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new f10f69dc6e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 1b072142b8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 22dfced7e8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 4d082bdb92 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 36e2a744a4 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new e9e465c4d2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 8a5b853dd5 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new ccb92d3a1c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2172492269 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 44763e529d 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new a55253f92a 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 135d44fdc6 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 473e062948 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 234ed5191d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 73595a9850 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new c8aeee86c2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 3f58f1b517 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 23db66c7bd 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 7c95834cb8 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2231baa3bf 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 45f9ebe3cd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new e2f4965e7d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 6f9fb9ff99 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 151549750a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new c9842de56e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d6d75ef033 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new e3b53d5e58 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 68b9f2b83f 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 9f9e0c46f1 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 1a7d54c7f9 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new b26e9cb019 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new c418179055 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 5e1f690802 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 153d4fc40d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 8e40a735a0 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new fbadd89aac 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new c8215aa813 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e2f881b33b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 76262ab3f1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 6682a6305a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c5b6cbc10b 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 9afbfab4b5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 473f1b2286 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new ac1f394486 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 1d2d32f955 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 4b07a761ae 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 7d92fdd148 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 2055011388 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new db4f1fb9e3 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 05b1936327 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new f5306d75a7 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 804cb28004 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 25bb97ffc2 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 6b625f96c2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 6d8d56b54f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 535db93f4b 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 60b6422638 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 4f275e855f 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 185e13509b 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 93593eac67 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new ae1c5021be 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3643128fb8 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 278e209ce9 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 0bdb35e85f 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 0c45c513c0 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 2804536738 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new e530286237 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 151ddf6895 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 3a8ef6fb2b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new fd7f89026c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 7899e6d30a 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new af6c68b4d2 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 7133afa250 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 09dec48261 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new d04ec4a0a3 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new a82ad6aef1 411: onsuccess: #2232: 1: Success after gcc: 3 commits new ab59596297 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 1178934c04 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 4d97d3c366 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 896e0e9806 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 9030b568c9 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new cb2c89c180 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new df7c1f4ef4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new a95058ad65 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 94814ddc37 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 8ad0d886af 421: onsuccess: #2245: 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 (232d98deab) \ 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 1808 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30996 -> 31256 bytes 04-build_abe-stage1/console.log.xz | Bin 89348 -> 89276 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 9064 bytes 07-build_abe-glibc/console.log.xz | Bin 235688 -> 235500 bytes 08-build_abe-stage2/console.log.xz | Bin 226808 -> 225596 bytes 09-build_abe-gdb/console.log.xz | Bin 38628 -> 39244 bytes 10-build_abe-qemu/console.log.xz | Bin 30924 -> 31428 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3208 -> 3100 bytes 13-check_regression/console.log.xz | Bin 5792 -> 5964 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 --- 13-check_regression/mail-body.txt | 42 ++++++++++---------- 13-check_regression/results.compare | 25 +++++------- 13-check_regression/results.compare2 | 25 ++++++------ 13-check_regression/results.regressions | 26 ------------- 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 | 44 ++++++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++--------- results | 26 ------------- sumfiles/g++.log.xz | Bin 2652504 -> 2646416 bytes sumfiles/gcc.log.xz | Bin 2212516 -> 2225980 bytes sumfiles/gcc.sum | 3 +- sumfiles/gfortran.log.xz | Bin 894352 -> 896184 bytes sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216960 -> 217160 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 445080 -> 440368 bytes sumfiles/libstdc++.sum | 27 +++++++------ 41 files changed, 140 insertions(+), 209 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