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 f905526958 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4dfb0f6f2a 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards cbf0a36724 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 1bf4fc9a1a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 5455c66b0a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 9ccca4196c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 2ef4cb4cc4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards b8d1657cd1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 153afa10a8 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards c25c912a1a 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards f08fb32c5f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 40beb573b6 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 3266fd9588 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 0318eb0903 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 269fdd86c2 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1033dddcca 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards a7ddc89b73 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 121d174e60 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards f972535fe1 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 594c56e008 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 5f5d3d3a5d 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 4eba33ac65 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4d1636bfd4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards cf6e941483 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 200cc10f15 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 24ff47e7c7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fa51239410 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 47d21d63b7 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 63f30c86b7 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 6312ae19fe 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 8b595a982b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 463f6cce4d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 3d048f52bc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards b069329300 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 11907dd85f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 9053e4f865 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 828268708d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 74de8e8cda 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 104fec4ec7 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f18f17ae8f 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e4d15161e8 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 5ddf92593e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards f4691e5a90 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 863c062534 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0962534b03 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 44a9a9b793 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards cc1b29e72f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards d724f3364a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 619246ef8a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 5f8748a38c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards c022e9f6ce 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 7199c8d395 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 6858b3c7c3 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards cdfce33717 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 95b7d31ab6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 578c5d2b34 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fae1848f77 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 434d12ce89 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 23a7b73d6f 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards cb4081fe1f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e3fcefd69d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards a7298c39da 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 3ef4fb9e7e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d524d14283 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2741ca8d8b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6d16deb7c3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 589940cfb9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards f1b2c85fea 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7da9ab6bf1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 7fd177386a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 54376ea16f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards e0513fc8d8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards b18d271778 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 4f182b987b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 3f1406329d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cf2b689f4e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards f4dccaec9d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards cdd0064c95 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e3e844a8c4 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 53c1f576e7 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards afd5805ff3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e379d65857 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards c67814c943 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards dbdd9066ed 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 06a1f066a8 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 8782e5d44a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards c723de0550 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6ef9a76270 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3c925468c7 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b3c9d371e4 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 8031a0260a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 57d70937b9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 656546537f 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 59101887fc 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 538520e440 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards f16f250004 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 6e0993e979 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 95819fe2e0 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 341a7b10b0 301: onsuccess: #2118: 1: Success after linux: 16 commits discards b9799e5713 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards ab986f1855 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 648cec1f91 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new e7028cee05 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0de8e6cd56 301: onsuccess: #2118: 1: Success after linux: 16 commits new 3472377c27 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 2fde9ca4f0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new f954da3388 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c97ebf29b5 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 38efe3ab7c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 06ef77ff63 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 480fef0e93 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 69b587c424 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6acfe58367 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 24ff816ef8 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 94120d32d8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 09be2e3a07 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 12d6dc4fa3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6a6a018c16 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 10330302fc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 54dd7f65f8 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 65036bf302 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 1f80fe9d5c 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 7bd3ae4357 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new ba1236d5bd 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 390c1c92d5 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 988317adcc 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new f2cf771547 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new adfac042c5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 64e615669c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 2a17bfb74a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new d37c8f4a91 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new da39d1e6e7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new fb9a3b9286 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new eec296dc1e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1a286398af 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new da6b9b5e9b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 5db7fb9cf3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 68b17709d6 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 456c9dae86 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a19e9cb390 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new dede05f3eb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 1de1896869 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 1c52732976 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 6a478892ac 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 57ee8eeada 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new e58b925bc2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new a4400e4c7a 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new ab1f7baeaa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 3c89e2f1a1 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 22b0690750 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 036864b453 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 5f19698b37 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new ef80e4ac9c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 70a409d286 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new c27e5d978e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new b45f1d2965 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new df17ce66ad 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d5094cf559 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b578387d6c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new f8a3492602 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 707eb03c94 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new f6473155b7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new fe482b4bb1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 4f976a8dbb 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new c7a928b329 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 5ae64d721e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new c7ebadd6bd 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e4264eaacb 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new f342f1c6b5 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 6855c2b1c8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new ee37bd3427 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new dea9e9d38b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 6ecf3962df 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 9e41d486c8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 22eda6175e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new caad44631a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e6ccdbea91 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 5e59d37cb1 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 45f4068a3c 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 91448c9a3b 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new a395938b89 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 86f1c55168 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 89e26fb08c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 7bd6326a8f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d116d702b8 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new fb74962b64 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new d7f7e8a781 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 6d2141e2fd 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new c9aa3d6402 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new c49bd644a8 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 489fda3bfc 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 51ad2e0f80 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 60b13d6d3f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new fe8c9c29ea 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 9b51c1cf7a 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 312b43480c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 71b04ca90c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 9e4f2f5476 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new c39e896297 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new d2c17b665e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new dabcc1324f 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new fa4e534be0 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 030fa5da86 400: onsuccess: #2221: 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 (f905526958) \ 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 1804 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31116 -> 31300 bytes 04-build_abe-stage1/console.log.xz | Bin 92084 -> 91264 bytes 06-build_abe-linux/console.log.xz | Bin 9220 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 236868 -> 236544 bytes 08-build_abe-stage2/console.log.xz | Bin 229660 -> 228376 bytes 09-build_abe-gdb/console.log.xz | Bin 38328 -> 38612 bytes 10-build_abe-qemu/console.log.xz | Bin 31828 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2908 -> 2628 bytes 13-check_regression/console.log.xz | Bin 6484 -> 6584 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 66 +- 13-check_regression/results.compare | 27 +- 13-check_regression/results.compare2 | 52 +- .../{mail-body.txt => results.regressions} | 73 +- 14-update_baseline/console.log | 60 +- 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 | 68 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 + sumfiles/g++.log.xz | Bin 2660544 -> 2636260 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2187636 -> 2184044 bytes sumfiles/gcc.sum | 2134 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 888840 -> 886396 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216956 -> 216976 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435988 -> 435244 bytes sumfiles/libstdc++.sum | 31 +- 43 files changed, 1289 insertions(+), 1333 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} (59%)