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 382db71281 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 90c1861e7a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5adf4c6905 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e85c42ee6f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards baa4e9f026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 130d146fe8 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7e7b8691ff 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c27e4e50e0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards aa1df27003 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 09acfbccc4 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c3d7915116 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f6f7d15033 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0cfa2975fe 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ba924830f9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 55077c694d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards ff1dfe811b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 2baa929582 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6a101f636b 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 5def288e1d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 1e37b1af8c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards cdd7f3546f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 4369399ce2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4ce7196d07 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a7b4b81134 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 037300bc89 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 2247aa0421 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0ccc744dc2 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c7760d663a 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 785a8080bf 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards db33f9b7f0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards f8d9b4c6b5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 626c09a700 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 1ebbcfd335 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 231b7e0b0a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 79881cb236 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5dc958c0e4 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards df357a5804 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 344d0e83cb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards b14f60e80a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards ed98ab7c9a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 9db98da9fe 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 1e58877606 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards f6af0b5f32 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 26a0ee1ee3 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 9fc3f28305 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards f961f1ede0 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards dd8062c907 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 0480dc8229 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards e1b4b39fc5 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 6e5e944965 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 9ea3885c2a 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d27b48926a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards df48415f00 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 289212b115 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards e298dd5e06 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 180e8ae531 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 4cbf720f24 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 2d072d9cf7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards e285c63fc6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 5d84bf8eb2 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards feacbeaafd 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 4720589aea 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2ce056c808 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 599a8003c7 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 0125d0c3ad 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 2aa75b111a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards e2cf38f5fa 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 1c7f2137e9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards db56c8a440 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 3e9294274e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 5247a8ce3f 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards e1a110b5ed 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 0bfcf641c4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards b4f41144c6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4ebbda8b27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards c18dc8ba87 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 651e632e73 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 280f0a1a1d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b9e8ce708d 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 3af9bf8ead 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 3434ce2d79 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 58972c7ed2 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards cb33236477 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 83232dccf8 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 4ab1fbd6b7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 42dd12a482 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 4a355a5d41 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 6f76c017bf 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 133219599d 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 9faa01ad78 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 9fdeb0cb33 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 1b5aa624ce 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 738bf38854 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 2495d57536 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 75c0d28c58 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b6f2855b45 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards a01a4fdab4 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 19d772eab5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 64410c3bde 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 11852a12c2 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 52a1cbad90 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 9fd8442178 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new ec1a731fa4 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new f87658c675 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 16dd521cd3 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 5066d8428d 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new fb2e9c5371 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 313b8e5d11 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 510e97cf9c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 9e506d4e27 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 0e4760c67b 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new d7439f15db 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 1a699288a5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new e13a91a07e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d25d330523 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 90b86be02f 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 7310117341 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 2d405308ac 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new d0653f51cd 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 8f959e2ef9 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new f6feca5120 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 48c14e0036 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 443c6a8d34 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b00f7c8b37 259: onsuccess: #2075: 1: Success after glibc: 2 commits new c28eee23df 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 8651caa5b1 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 3185ce54eb 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new c31bad6528 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 351a142748 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 5d91a0b622 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 589f3b661f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new e55fab4778 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new d7560234cf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 224727fa77 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 5a99732ffa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 2133097903 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 52a3470d4f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new f0742b46c4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 6ee1229d8d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new efe71d53a8 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 11eba28624 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 8fea2e2478 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new f5d617337d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 5bf492a834 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 10c89669d3 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0846d21e0d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new a3e7fd9629 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 86f0d9e4a6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 1532cf60cc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new f0d8874c08 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new d3a853dc2f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new aace657f0b 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 06296e3200 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new bb948e8679 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 953a9e0bda 290: onsuccess: #2106: 1: Success after gcc: 2 commits new e227485925 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new d13c7b535f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f435c8a134 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new eb6af7e2d1 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 905eea02ea 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new ae8964fcd5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new e801bdc2dc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new c743e1913c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 94ac56ccfd 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new bd13abde5f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 54df098fc9 301: onsuccess: #2118: 1: Success after linux: 16 commits new 842b907aec 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 6c6dcc3b94 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new aa4e1b990f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c842547108 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 94eb3f240a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 258b0ad99b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new beba477af4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 2bf4d63ac0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 0abf07a7ac 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3e8acd3842 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 4de16cba36 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 6a47a3cc55 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 054e4f4fe6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 74839e3821 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 096cf9a679 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 2b3992cb4a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new b5525afae1 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e0581285d2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e38fc2890a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new d4bd0f8b82 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f60bdffc7c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 3c4a831787 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 877a8585df 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 687a7fc5a5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 26120cf094 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 070ae1337e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 814ece578b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new da12eb2a96 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 67f78dd3ee 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 9b952680b4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 52d5ca79fe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 12f05d3937 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 1cea275183 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 88366e0bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9838d09c2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a340ef4375 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 64e52e6482 338: onsuccess: #2158: 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 (382db71281) \ 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 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31868 -> 32252 bytes 04-build_abe-stage1/console.log.xz | Bin 92112 -> 93076 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8704 bytes 07-build_abe-glibc/console.log.xz | Bin 236052 -> 237964 bytes 08-build_abe-stage2/console.log.xz | Bin 227920 -> 231568 bytes 09-build_abe-gdb/console.log.xz | Bin 39376 -> 39648 bytes 10-build_abe-qemu/console.log.xz | Bin 31172 -> 31492 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3224 -> 2544 bytes 13-check_regression/console.log.xz | Bin 6364 -> 6304 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 | 21 +- 13-check_regression/results.compare2 | 41 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_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 2690728 -> 2689380 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 2226068 -> 2258412 bytes sumfiles/gcc.sum | 1842 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892088 -> 898892 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214172 -> 214088 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432284 -> 440428 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 1064 insertions(+), 1159 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