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 d9c2e15c86 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 95c4cb1966 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 0a17151a77 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards eeca83781a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 68023ec231 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards bf0577c2be 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 67632a82ea 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards e93ee41472 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ffff3b0cbc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2dfc3f9a07 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 74d06a9c7a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 9dcb09b345 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 980662f8ca 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 5236f5dcbb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards e753820f47 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 7da0e48e1c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards dd3f732de4 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 80e6adbdf7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b6e4d11dde 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards a1c8ee0891 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 96f810bd56 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 853cb2976f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards d1d5cf3c3c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 68be55e2ea 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards fa5c8b94a5 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6d1fe995af 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 1084c8f45d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1ac0556465 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 503494f2e3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 121cdbd9c3 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 047f97e0da 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 7dda451f82 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ed290f1845 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b00fd43e99 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards ccabc5b122 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 666b2a8213 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1a2a811525 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 626d2675ee 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 1b8ec06a6f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 93c969ac91 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 2f7b95e4dc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards a90c80ab3f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards f08d03b669 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 37a3377b5c 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b2d1543a87 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards e6d377f160 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards aca4c41adf 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 71405c0085 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 095ef7edda 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 30d39c2452 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 1bf9b26163 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 320aa77326 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 6e191ef572 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 60ffa70fbc 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards fe683f144b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 92af2fb105 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 2f3a66611e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards e3b8afd69f 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards a07817aaf3 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards b144a5339f 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f5645166db 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards c54ba770de 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 53e80db0c2 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 974b6331e6 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards e5034cccbc 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 0805d4500a 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 77a25a97a4 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards adcfb42fb4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards be4c56006a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 92f8a4b0d0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards dd2f84dcd5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards d3dfad1485 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 9baec8b58e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 5fe5a2c663 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 980364d4fb 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 8a606c2d87 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 3d25d337de 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 391e94d39f 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 96819ec8ae 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 03afaf08c9 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ae1a7b60fe 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards be6b88230f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 8e05f8130f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 17c358874f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards c1d58afe4c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 7090d821b1 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards e2cccc10d1 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards d3329a7d8c 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 2e612b2d6d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 4e6d63fdd0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 3974b3401b 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 8a575110c2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 6c7e863c66 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 06a64bb3f7 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 77d941a6ec 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 0d337a688f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 4e04f265ba 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards c1e888530a 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards cd351f9ac7 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 8cb76f21c4 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards ebdfa705f2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 6bf1769b72 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 60e5bed64e 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 161df35835 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 9b329fd0eb 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new e8c23d56f0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new ed6e2971c7 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new e1b4ed71d7 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new af88f90609 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new bc8e609fe9 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new d91462282c 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new a81c4e7c61 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new b1e37a2ea2 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new d5dae12f5c 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 1d7e485765 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new ee952509ae 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 8d239093f3 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 91823cbd05 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 11de73abaa 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 212dfced0f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f48650a98d 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 25dcfa8eb7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new e0a78362ad 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ac9eed1980 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 345dc5dba6 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 26b2086fca 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 525b09a193 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 2d76458302 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new e8c9dd3341 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 66091e94f1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new c97fb8931a 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 5e04af9c87 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 91cf370f18 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 49b804f600 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new c9203cef6e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new adaf79cd85 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 62ef65baf3 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 293106e532 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 4d98009521 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 3381d15874 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new f0c9840d4e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new a1814291c0 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new d6a3e2b114 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 870bf09e75 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 6cb80736f3 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 7eae872dc0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 953ebd29bd 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 384ae5017c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new b54d0b3076 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 18e2eae8da 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 462cee8d88 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 77229854c5 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 7cbe8b145b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new be90f395dc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 0e99c48edf 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 805e4adc90 294: onsuccess: #2110: 1: Success after gcc: 17 commits new f33ab5f8e3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c69258f14e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new b35ae24de8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 705172a87c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 7d73d44051 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 3b7e80d0bc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 7263fb1d31 301: onsuccess: #2118: 1: Success after linux: 16 commits new 8debdb7aa1 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new d289af6f89 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 7d1a8d2b42 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new f803664b08 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6a247e29bb 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c621a39092 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 7632ef6b9d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new f1f416a63a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 80d05d0858 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 20a507df4b 311: onsuccess: #2130: 1: Success after gcc: 4 commits new c4efa65d26 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 7eabd23d6a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 2bb7e27734 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 16383186a1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new edd523d8df 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new c80c8e0ad7 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 166bfaf983 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6c60470563 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7211769ed5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 203c59616d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 581380767a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 70412d2f58 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new ab66d4fc4c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 8ac10480e2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b587af8789 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c545704baf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new fee8bc0404 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 29747260a0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 32c6cdd5ce 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new a27060051c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new fdc1122c8a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 38b8eb6e30 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2797bc6a0a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2701deffa9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 3cf9343ac5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f91b3ed9a5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 54a9552afc 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new cf169c4d93 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new a0df453a28 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 646b053a7f 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...]
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 (d9c2e15c86) \ 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 1784 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31824 -> 32080 bytes 04-build_abe-stage1/console.log.xz | Bin 91720 -> 91816 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 236000 -> 235956 bytes 08-build_abe-stage2/console.log.xz | Bin 228824 -> 228592 bytes 09-build_abe-gdb/console.log.xz | Bin 39272 -> 39524 bytes 10-build_abe-qemu/console.log.xz | Bin 31136 -> 31780 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2908 bytes 13-check_regression/console.log.xz | Bin 6360 -> 6020 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 | 9 +- 13-check_regression/results.compare2 | 58 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 42 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2692248 -> 2690064 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2246972 -> 2243212 bytes sumfiles/gcc.sum | 2143 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 897412 -> 899784 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214240 -> 214052 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441816 -> 433140 bytes sumfiles/libstdc++.sum | 6 +- 42 files changed, 1213 insertions(+), 1264 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