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 7a895be0f8 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards ffe3343973 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 7176015a5b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards eecbdf7c2c 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 98e3d5df91 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards c43dd6a5d2 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 963e42ce41 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 23b6789c06 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 8d1d7e3fbb 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 62ec704db0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 1f4f169c31 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 2e684fe1d4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 40af0bab10 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 84a591e0c2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards aa3f143a11 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 3755c8c37b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 988b0ec240 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards adb1986a71 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 7be09f720f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0c1490f4bc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 91c05f2d82 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 455eba624e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 3d9578e9b5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards bd89dc5a8b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c9420a677a 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards cef2cf9ca8 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards ea1ba30b66 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards a81f791f20 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards aa1760d3d9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 328c944d05 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4df578cca4 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards b1d4b1868a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards bcf0b3811d 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 5a78f4eba8 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards bcf44f60c8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 39bc88570e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards e623f2dcbf 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 068097d736 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards c6226648d0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 9d9cd3a35e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 1b4214e123 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 14dd815920 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 902363c34e 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 50478702ea 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 2ebfab827e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e5c8984419 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards ea50967208 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 4265a9c7b7 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 47e1fbc3de 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 20059e61b7 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards fbb1efe8fd 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 1f141bcdba 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 97c70e7c67 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6ee94b987c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 1e68a39d78 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards c8589352e2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 006bead909 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards f6e6477837 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0a1f4c2144 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards d33dbd2b76 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 79d08b4d07 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 426d8cce22 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 818335068b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards a128fd26fb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards bd77d30b02 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 1f5be54c2c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards ad1e5646e8 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 3cc197e27c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d0c6a0a7b3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b7f739578b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 84857818a1 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5050f53474 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ef2ac39d8c 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ffa4534dae 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 03967a8485 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 4620013fe5 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards f27d5523e9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 425cac2810 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards eed0d8f73c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 1338f2dd2c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cb4df6717c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 187cf237a7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 6f6ec5be01 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards f5f4f7f7c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c3d5879b7a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 1210658edc 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 614f5914b8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 0bee63f8e4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards d618834847 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 52ab4914e7 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 9bb606ef46 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 5ad2b9f601 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 374b949d7e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 11752753ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 175c4c315c 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards ba630b0cc4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 2c42d26e7a 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards a5b387aa32 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 61212a68dc 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards cbfb22146b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 4b3d1ade1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 01d8b3394d 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 85455621b8 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 56de47ac3a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 9525f110a4 307: onsuccess: #2124: 1: Success after gcc: 2 commits new ef3c11a85d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new d93d000d80 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 757826dddf 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 7631066e65 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 75f2f2cdaf 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new a107f5c7d3 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 314b0007d7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new bb0c92d400 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new aba2917571 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new df3443a02f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e0b812896a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6fc9230717 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 69c1d97bf5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 43f7a669fc 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 467cc45d01 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 8b16cdac74 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 831a7c34dd 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 6bbbc61ff0 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 81acad385a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 3cda2228ad 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 6a033b3607 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 9a051a0806 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new f17a852849 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new c76e0b2517 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6152842623 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 8c02dad5a2 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e5fefd6f2d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 91de17c4a8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 406a7786e0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 606302d7d4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1bee113593 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2f4e063891 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 51a8d3f9aa 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new fbe6d4e3d0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 660e37be3a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 531684be5f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new b97222969c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new eef459153b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 4cd0c43485 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e1652bf4cd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new de8a85dbce 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new ad4964b07d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 7d6ad82c33 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ea350e68d3 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new a0a40433d8 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ebf1835c08 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 62b382b1a9 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new da360d8420 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b8ae11c5c6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new c7bfd17752 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4ed6af3b25 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 21a4cb517e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new f8265f82e2 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 35147c4989 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 556fece504 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 95cb480ffc 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new ce186ac990 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new dbea2650f4 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 83ae8652d7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new ed9793814f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new d4e354845b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 26edf89cb7 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new bc80309c08 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 688b652346 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 5d28ce2da0 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6ad3d6a3e3 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 55ac0c804c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new ef66364938 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new cd1b3590c6 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new c9ec752cce 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 4542dc821a 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 448164d5bc 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 898a31d8fb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 6485a10f7f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new aeb8613820 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 5bb5e897d3 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new c02e7cefff 384: onsuccess: #2205: 1: Success after gcc: 2 commits new f043bf461b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 88893a173c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new e6b55ad585 387: onsuccess: #2208: 1: Success after gcc: 2 commits new da208cdb5b 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 3622435084 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 2c4b5d4f26 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 44a240f352 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 419a944e35 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 7579d512d2 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new c38af894c3 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 253b7f2e0d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 30b403e2a7 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new f4e54d4a85 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new e2a5da6958 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new b5ff087a04 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ae464b9a41 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d53e842703 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new ae04fba122 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new b2b7df181a 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 7750a11e99 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new c0fe77fb21 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits
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 (7a895be0f8) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31388 -> 31000 bytes 04-build_abe-stage1/console.log.xz | Bin 91608 -> 91196 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 236972 -> 236420 bytes 08-build_abe-stage2/console.log.xz | Bin 228768 -> 229812 bytes 09-build_abe-gdb/console.log.xz | Bin 38664 -> 38336 bytes 10-build_abe-qemu/console.log.xz | Bin 31928 -> 31192 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2776 bytes 13-check_regression/console.log.xz | Bin 5968 -> 5924 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 56 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 8 +- .../results.regressions | 57 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 58 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 26 + sumfiles/g++.log.xz | Bin 2641368 -> 2679548 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2202220 -> 2200148 bytes sumfiles/gcc.sum | 2036 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 891556 -> 895192 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216836 -> 216924 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438260 -> 441416 bytes sumfiles/libstdc++.sum | 29 +- 41 files changed, 1179 insertions(+), 1239 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (59%)