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 ea4d19579f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards f794131d3d 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards eb1de7aafa 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards eee1535d31 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d213d46d60 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 04b3521e22 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 960575e8b1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8886f67c93 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c03f7068dd 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 98efaa5fe4 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 12a4905480 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards a0af3ba71f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 5701d010ce 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 3afd35b0ad 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards af9eaa8a75 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 54e81c1f1c 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5d8ede864f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards cfcf79bdbd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 11ffeb9439 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 5fbce18234 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards edbfbb8705 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 7c4c8e63b8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 58d240a2f8 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 07aaafb08a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 1b5a96acb9 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 7e954f96d8 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4505d51d73 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 596e768e7a 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 37d8e2af01 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2503c7e9f8 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 86255ad1cd 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 46d8790b13 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b78efaffd1 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2648d4262b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards bb12cd6f58 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards edf1815746 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 763979fba5 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f437a68809 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards f7002918a5 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 09709c95e2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 8ac991ab3b 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 1a11323319 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 28bf3d64bf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards af5d99f714 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 69b62688c0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 75e7b48237 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 5d894a7544 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 585b7fb908 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 95107df2e8 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards cca4623cf1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards bd68cb722e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 256dafcb8c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards cd2f6ff072 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9c6f057495 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6a8991d56f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c50f38d08e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards f6c64b7c8e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7a119a0e4b 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 79fb2e3240 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 779d1cc596 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards d702d55100 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards bf336c38bf 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 6735d02fe8 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 7109d2af16 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ea0b0b9fda 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards b001af0fb0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards ee651b2894 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 1741a4d6f3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 64da8ad6ed 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 63cd4ba5c2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 2d2da88f84 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards b52fd16d1b 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 7adb44e895 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1c43886ac6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards dbde1589fc 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards a8557cc42e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6a8a28fab9 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards b440b06547 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 946f093370 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards ec4c748b7d 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards c1d4b4e2b0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards fd3c06ed98 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 356131bbc6 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards d590150d65 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 0033d80c8f 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 700f8140c7 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5f7cf79ca9 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 3a9a376812 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 737ac0807b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 37b197ca08 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 76ef9cdd23 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 7e17690514 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 8527de0ed2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ac6003bba9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards a76981fa80 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 62185bf800 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 98ca4dad75 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 25f882cfa9 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 4e56fca876 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 5b8933682c 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 35ef222810 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new e5e72c22f7 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 5dc5590134 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new f3199990a7 290: onsuccess: #2106: 1: Success after gcc: 2 commits new b7b8dc2f96 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 9ee0b8bbe0 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 43d79e17b8 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 553e8fc57e 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 86715c09a6 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new e0de2ad89c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 323de1cbd4 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 896dbccf1b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3dbf94f15e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 8e746b38d8 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new a56d1d15e4 301: onsuccess: #2118: 1: Success after linux: 16 commits new 399c868675 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new a09ddc76ad 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 784bbf1b0e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 3a6b9b2e6c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 6967774005 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 8a02e8df40 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 1459c9d44c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new f7d13f520c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new a904fdf953 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 10659dbc57 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 0391407153 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 660f7f5583 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 0cc0d2ac30 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new f26c6622c2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new bd3ecf09df 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 53fa33e977 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 266f648350 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new a7b890c3b6 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new d56b44a6bd 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 68cd2b4ae7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 8169d75682 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 039e00047c 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cfd6257bb0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1decbf53f8 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 96ff2fc922 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 2352f426d3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new e59ff2a9af 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new bd41bb309c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 3def0c1673 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7ee0b8c34a 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1be303d636 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 3a556cc924 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2ea59f84cc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 951d14661d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 36f86b9bb0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f1439babed 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new d79ed03ec9 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 828a734e0c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new ddf588b514 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new d3766ec202 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 2c179f69ed 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new a74068a87a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 878511a327 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 309e23fdb3 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 5f0f4d4399 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 5c76793ffd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 5021b6f4c7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 5f642dde2f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new c0d42b85dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 37770bdd68 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7e9fcc8833 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new e1a7449fe0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 65a126644b 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 2247701797 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ae4d674a2a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 414e5c3952 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new b5d565b204 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 0feacf361f 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 8b26dfd980 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7f1588bd34 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 95080b7445 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new b63aed7494 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new c7f8db1553 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 367990c81e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new f4ba078e48 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 94842d483a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new f7c2b38037 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 5b4c4f4308 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 99c063d0d1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 92833f0e74 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new af3b2dc991 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fd58d37824 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 9bf6a96546 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 97d48f6c36 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 798448798f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new bbd18ea0a1 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 1aa4cfa9c5 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c42179ae27 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new fc30234be5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new ec73b950c5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new dfbc50a407 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 866e531469 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 69c99707c7 384: onsuccess: #2205: 1: Success after gcc: 2 commits new c79be3063b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new cf642a6b51 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a0957cd0f7 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 7e7e9623c5 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 893faf52f5 389: onsuccess: #2210: 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 (ea4d19579f) \ 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 1772 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31236 -> 32560 bytes 04-build_abe-stage1/console.log.xz | Bin 92636 -> 92952 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 236244 -> 237400 bytes 08-build_abe-stage2/console.log.xz | Bin 232288 -> 230544 bytes 09-build_abe-gdb/console.log.xz | Bin 38500 -> 39660 bytes 10-build_abe-qemu/console.log.xz | Bin 32360 -> 32820 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3024 -> 3368 bytes 13-check_regression/console.log.xz | Bin 6452 -> 7168 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 52 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 55 +- .../{mail-body.txt => results.regressions} | 59 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 26 + sumfiles/g++.log.xz | Bin 2655836 -> 2649380 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2227076 -> 2237304 bytes sumfiles/gcc.sum | 2415 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 894056 -> 896584 bytes sumfiles/gfortran.sum | 5 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214332 -> 214624 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 440688 -> 439956 bytes sumfiles/libstdc++.sum | 61 +- 45 files changed, 1415 insertions(+), 1478 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%)