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 3e1ae6c942 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 401db15e65 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 0946d8c8c8 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards ed9b581007 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 67bb2d8ad3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ade1b88aa6 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 11767afc99 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards eaaa6f7de0 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards abf9c0f610 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards e9b1e70f74 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards dd79fe5de0 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b0a46fbde7 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 9a916c8494 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 049582dfd6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 258d27aae7 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards aed9e34b43 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 41bef723d0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards ba5e6463c4 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 9353c1cd42 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 20413b7995 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 7b62037851 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 9dbcb38dd9 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 0fadd452c3 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards cd2fdd7c32 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 76e727d3cd 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards e281982eda 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 35f8af4dc4 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 76acd96486 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 39e6ba5f2c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 49ff55c0c4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards af1d696911 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d78c72bc5f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 280687ea2d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards ea8169bf06 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 81d2a04a49 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 5b30e4c1eb 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 0c4a965a1c 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards c2f7bb2ecd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 25fbe27b77 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 6482a0a157 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards da9b2e7eec 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 653f5661de 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a3000880d5 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 15f50eb0a9 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards a107973c43 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d4777e359f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 0e3b3c5363 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 306c31f6e8 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 375651becf 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards cad4fb164c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 44cd670ed9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 27cd54537c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8b7df84579 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d0344b8366 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards c24440f532 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 458e94dd0c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards a29623727e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards bb06016192 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 2c95d9caf5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 781227270e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 4fea4ff138 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 058c3386d4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 20c73f77ce 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 28b272fd15 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards da68e3420b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 9e2a632d02 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards f5a4ccd403 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 5cd9ad231f 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards aa10ebc7df 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e9ce6be0e2 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 1d8a57a7f7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b8d6b29ca9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards f76745864f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 51ff12ae95 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 0eb89cc67a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards b5e7e026ec 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 6fbe61e312 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 156193832d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards ec9e3593bc 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 94f78a63f2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards afda0dc01d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards ab6b2faef2 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 2a17452d06 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards badaa00d8c 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 0750e67be2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 16f1768ea3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 80a6122807 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 54ddec5681 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 5c37ec0d53 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7efeabbfbd 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 7e93396b7b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 021f88c113 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards fb3c208251 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards dde446b6fb 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6b3b2cd392 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards fdd58f95ed 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8b54ed4d31 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 148a912f1d 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 7a3e5fb877 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b32c60b1a0 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 02dbb33c89 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 38019cb203 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new b86ae5f31c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 283af43ad1 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new cb8e0ad290 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 5df8561d7c 310: onsuccess: #2129: 1: Success after binutils: 4 commits new f487730857 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9237408ab6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new fa4eacf721 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 548ce13611 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new d08a5bfe79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new d0798f7bf6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 43b6e101df 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 69f1b591e8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e131d7418f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 095fa54700 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 8eb17d9316 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 8f3d875153 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0d2c572f64 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 990a99708e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 5faf6b3a1a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cbb0152f82 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cae80273af 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 285c14716e 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new a2519f12c8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 5cb46f3b05 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e95faca4e8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c4dfdec98f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 3f90243009 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 54dde8ed6a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new ef505445b8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9afa398da2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new afa9b44d63 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c406ad1018 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 1beb5183cc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new e72d828884 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new e99fe04b05 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 5f5a243fca 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new fc755a63eb 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new bf9e375342 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new a3bfdcb804 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 8ee9b28539 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new db5bd77494 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 1c77b03c50 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 778cfd326c 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new a39e8f6c72 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 1b00ad2374 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 07e228b957 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new df473b493a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 3da6167ac3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 313c1df9dd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 61dec95a18 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 7ac6166c20 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 0f75f8d9de 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 1168a29bdb 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 4928fdb092 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c6d44f69ac 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 86324a1792 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 1b15163fdd 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new aa2cdde22c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2c936cb8ce 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 0615b03e29 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 95ab4eab16 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 0cd679a3e5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 9af97e876e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 1ceede6a5b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a8f582d91e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new b142b73545 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 11327ec5ce 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e1c353648b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 60c5acc93a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 3c39569c7e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new d654fe0abd 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 3545ddd447 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new ed65c295a3 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 65f020e52b 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 9143596843 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new e39f92b38b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new ec2db6717f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 6ab890fdac 384: onsuccess: #2205: 1: Success after gcc: 2 commits new eeb4fc645c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 3671874d07 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new d6bf70032a 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 604078c5d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new a0875e2108 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 70ecd7951b 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 461452133e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new aea1dc2762 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 65bfd50cbb 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 3f545e4f66 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new b1535c5af2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 11afcf3fdc 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new f8baf9605d 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 71bed2a178 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new f3f1c9b43b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 973093ceaa 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 578a92e522 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new d66d7ddfcb 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 0ba59f2241 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new b417f833ba 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new d3301d7980 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new ad37064fd2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new aff339e825 407: onsuccess: #2228: 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 (3e1ae6c942) \ 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 1768 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31036 -> 31028 bytes 04-build_abe-stage1/console.log.xz | Bin 91700 -> 91412 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 236820 -> 236372 bytes 08-build_abe-stage2/console.log.xz | Bin 228504 -> 228632 bytes 09-build_abe-gdb/console.log.xz | Bin 38284 -> 38340 bytes 10-build_abe-qemu/console.log.xz | Bin 31860 -> 30956 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2768 -> 2792 bytes 13-check_regression/console.log.xz | Bin 6128 -> 6080 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 | 34 +- .../{mail-body.txt => results.regressions} | 43 - 14-update_baseline/console.log | 62 +- 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 2629076 -> 2662376 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2184156 -> 2199044 bytes sumfiles/gcc.sum | 2338 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 887292 -> 892396 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217032 -> 216984 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433732 -> 443340 bytes sumfiles/libstdc++.sum | 32 +- 43 files changed, 1357 insertions(+), 1378 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (72%)