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 c0fe77fb21 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 7750a11e99 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards b2b7df181a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards ae04fba122 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards d53e842703 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards ae464b9a41 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b5ff087a04 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards e2a5da6958 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f4e54d4a85 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 30b403e2a7 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 253b7f2e0d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards c38af894c3 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 7579d512d2 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 419a944e35 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 44a240f352 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 2c4b5d4f26 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3622435084 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards da208cdb5b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards e6b55ad585 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 88893a173c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f043bf461b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards c02e7cefff 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 5bb5e897d3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards aeb8613820 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 6485a10f7f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 898a31d8fb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 448164d5bc 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 4542dc821a 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards c9ec752cce 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards cd1b3590c6 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards ef66364938 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 55ac0c804c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 6ad3d6a3e3 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5d28ce2da0 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 688b652346 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards bc80309c08 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 26edf89cb7 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards d4e354845b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards ed9793814f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 83ae8652d7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards dbea2650f4 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards ce186ac990 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 95cb480ffc 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 556fece504 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 35147c4989 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f8265f82e2 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 21a4cb517e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4ed6af3b25 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards c7bfd17752 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b8ae11c5c6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards da360d8420 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 62b382b1a9 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards ebf1835c08 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards a0a40433d8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ea350e68d3 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 7d6ad82c33 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ad4964b07d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards de8a85dbce 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e1652bf4cd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 4cd0c43485 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards eef459153b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards b97222969c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 531684be5f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 660e37be3a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards fbe6d4e3d0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 51a8d3f9aa 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 2f4e063891 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 1bee113593 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 606302d7d4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 406a7786e0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 91de17c4a8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e5fefd6f2d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 8c02dad5a2 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6152842623 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards c76e0b2517 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f17a852849 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 9a051a0806 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 6a033b3607 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 3cda2228ad 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 81acad385a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 6bbbc61ff0 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 831a7c34dd 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 8b16cdac74 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 467cc45d01 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 43f7a669fc 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 69c1d97bf5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6fc9230717 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e0b812896a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards df3443a02f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards aba2917571 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards bb0c92d400 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 314b0007d7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards a107f5c7d3 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 75f2f2cdaf 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 7631066e65 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 757826dddf 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards d93d000d80 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards ef3c11a85d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9525f110a4 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 56de47ac3a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 85455621b8 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 23db084167 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 02dbb33c89 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new b32c60b1a0 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 7a3e5fb877 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 148a912f1d 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8b54ed4d31 310: onsuccess: #2129: 1: Success after binutils: 4 commits new fdd58f95ed 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 6b3b2cd392 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new dde446b6fb 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new fb3c208251 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 021f88c113 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 7e93396b7b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7efeabbfbd 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 5c37ec0d53 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 54ddec5681 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 80a6122807 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 16f1768ea3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 0750e67be2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new badaa00d8c 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 2a17452d06 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new ab6b2faef2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new afda0dc01d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 94f78a63f2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new ec9e3593bc 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 156193832d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 6fbe61e312 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new b5e7e026ec 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0eb89cc67a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 51ff12ae95 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new f76745864f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b8d6b29ca9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 1d8a57a7f7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e9ce6be0e2 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new aa10ebc7df 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 5cd9ad231f 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new f5a4ccd403 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 9e2a632d02 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new da68e3420b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 28b272fd15 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 20c73f77ce 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 058c3386d4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 4fea4ff138 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 781227270e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 2c95d9caf5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new bb06016192 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new a29623727e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 458e94dd0c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new c24440f532 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d0344b8366 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 8b7df84579 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 27cd54537c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 44cd670ed9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new cad4fb164c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 375651becf 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 306c31f6e8 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 0e3b3c5363 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d4777e359f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new a107973c43 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 15f50eb0a9 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a3000880d5 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 653f5661de 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new da9b2e7eec 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 6482a0a157 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 25fbe27b77 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new c2f7bb2ecd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 0c4a965a1c 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 5b30e4c1eb 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 81d2a04a49 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new ea8169bf06 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 280687ea2d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d78c72bc5f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new af1d696911 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 49ff55c0c4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 39e6ba5f2c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 76acd96486 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 35f8af4dc4 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new e281982eda 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 76e727d3cd 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new cd2fdd7c32 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 0fadd452c3 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 9dbcb38dd9 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 7b62037851 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 20413b7995 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 9353c1cd42 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new ba5e6463c4 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 41bef723d0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new aed9e34b43 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 258d27aae7 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 049582dfd6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 9a916c8494 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new b0a46fbde7 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new dd79fe5de0 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new e9b1e70f74 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new abf9c0f610 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new eaaa6f7de0 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 11767afc99 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ade1b88aa6 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 67bb2d8ad3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new ed9b581007 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 0946d8c8c8 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 401db15e65 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 3e1ae6c942 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...]

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 (c0fe77fb21) \ 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 1752 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31000 -> 31036 bytes 04-build_abe-stage1/console.log.xz | Bin 91196 -> 91700 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8776 bytes 07-build_abe-glibc/console.log.xz | Bin 236420 -> 236820 bytes 08-build_abe-stage2/console.log.xz | Bin 229812 -> 228504 bytes 09-build_abe-gdb/console.log.xz | Bin 38336 -> 38284 bytes 10-build_abe-qemu/console.log.xz | Bin 31192 -> 31860 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2768 bytes 13-check_regression/console.log.xz | Bin 5924 -> 6128 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 | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 26 - sumfiles/g++.log.xz | Bin 2679548 -> 2629076 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2200148 -> 2184156 bytes sumfiles/gcc.sum | 2198 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895192 -> 887292 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216924 -> 217032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441416 -> 433732 bytes sumfiles/libstdc++.sum | 30 +- 43 files changed, 1262 insertions(+), 1319 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