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 4e7bd31901 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 6e5eac421b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 5dde09f6e5 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards e0b146cf62 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards ac61a266f9 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 026805f652 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards d8276f4514 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 337df0e301 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 2219f36b47 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 157133e8cd 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 4ff4fd4846 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 9e1caac301 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 42b14bcd3b 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 424160bd7f 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards ab2755f36d 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards e766c358ef 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards c0130ad6e1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 5546b82897 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 231fe25f81 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 2b92351d42 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards d97b627f2e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 9627d86d17 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 61a675d784 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 8c36aed1ea 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 2306f13542 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 44620aed4d 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 6923dbd250 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 50bb32e71d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards e17b00f7c1 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards b8cbb1dc38 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 56396e6e4a 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 9760832e2e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 403a5a0edb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b63b60392a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 2fa1e31d9e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 8c99ce694b 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 89992aeb33 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards f0b946d023 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 0793f5fb9d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards a7c0415f9c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards ce3a9fba72 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards c0bef9072e 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards ad28d14c6d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 142fb1c320 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 65bd718444 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards d7e455e039 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards cf7f5cbda8 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 77550d7f99 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards dffabe1c2e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 3b0d8b90ba 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 63e7a6c19b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 1d60f498b9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards c576036ee3 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards a4d40904e7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards cca9caf1fd 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 8e14b27e9d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards e09f366da1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 732f70675c 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d122b7629d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 7670c8afb0 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 55ccd2d957 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 12ab00ef45 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 1ba980383d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 695705ddd5 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 6b01c1bb82 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a9f1d8f908 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 9699789ef5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 94b950a0ec 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 97ebe1a32a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 3d48eb87fb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards d4880e3be5 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards d89a4feb5d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 9093b550fd 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0580e33dcf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 94e80e3afb 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards d4d19635c7 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 64c4578f1f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 688090a82a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 183b69e39a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards c3b833edd9 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 2b795fc724 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 6a9e6f27fb 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 106bfa2b59 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 198e70206e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2d52abe172 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards cc99ba9853 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9216a9a262 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6423410919 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 6a6ddeca5f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 550bda28f0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 841555d0cb 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 3081390de2 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards d655042b70 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 57be9ef200 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 79cf774821 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 143561e8d3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 5f0a4a7d66 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 798088780b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 3e651ee97e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards f8df813beb 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 0e923a6869 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new d3a62375e1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e4f1d42654 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 5f9458828d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 48bc6e7599 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 72864ee627 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8945aef19e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 21170a6483 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 295dea88fb 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new a2f1e45624 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 1aab61e830 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 3a0460554b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b289e31939 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ba095a9fa7 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1d267483b4 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 332dfc4959 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a9e9da9e9b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 16f461f651 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new a6bb88e55f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 95e23dd75b 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new fa41ba01f7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 27571f476d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d2c6194a27 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 3e1e5754d8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b102d8c093 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new fb07aee708 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new ba12cb832e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 2283b47daa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 8ed1a137a4 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 4bbd02cd41 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 21eeba746a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 11f2c1ef3d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new d561ad71ff 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 132f614c04 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 8fc5e00ead 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new e7eac36b5b 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new b42d7cbb0e 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 282707f72e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 39380334d6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new f92757f0e8 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 9b76b4d963 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 79e534bbf7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 0806f6446e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 20cda52381 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 946ede4015 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new ac9d108e2b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 54d9eec41c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e32a5b964e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 6a8992a57b 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 494f06b1e6 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 1ec07ceafe 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new eb29b32692 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 4f18aa3ae2 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 6703aa5b0f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 038f373baf 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 0142ff4cb3 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 2926d554dc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new af86305a49 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 13aeeb2feb 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new b80ba16062 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 1888cefbc0 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new da9399f035 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 0b3178fb85 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 7f47b69c4b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new f870977342 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new f3a3da9f08 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 2113361b1f 384: onsuccess: #2205: 1: Success after gcc: 2 commits new d95c737a09 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new b2397d9a15 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 6fe6220ce4 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 77c4fb184f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new fedccd3245 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f9f591e4ce 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new c1d61e4714 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 8b25fdbd52 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new ee4eaeacae 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new cb65633f61 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 0a6027ba92 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 9dda0d4d78 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new e6a5722431 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 1cda530fe6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 203f79ea16 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new b216b415c5 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 4bd8a1db60 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 24303c9425 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 795eda0e1d 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new b1b5e411a2 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new b6f87c558c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 6520bf04dc 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new ea0083b0af 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 0ca678a514 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new d984ad2de3 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 74f431497d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 6737423dad 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 9cf208c89a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 53d57cd85b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 4a6b483752 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new e3cb90096e 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 8aa60b6646 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new abf3325c31 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 9e1695216e 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 9cb2abe2d2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 232d98deab 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 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 (4e7bd31901) \ 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 1776 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30932 -> 30996 bytes 04-build_abe-stage1/console.log.xz | Bin 89172 -> 89348 bytes 06-build_abe-linux/console.log.xz | Bin 9028 -> 9080 bytes 07-build_abe-glibc/console.log.xz | Bin 236736 -> 235688 bytes 08-build_abe-stage2/console.log.xz | Bin 225144 -> 226808 bytes 09-build_abe-gdb/console.log.xz | Bin 38852 -> 38628 bytes 10-build_abe-qemu/console.log.xz | Bin 31744 -> 30924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3820 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2720 -> 3208 bytes 13-check_regression/console.log.xz | Bin 9132 -> 5792 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 ++ 13-check_regression/results.compare | 21 +- 13-check_regression/results.compare2 | 497 ++------------------------------ 13-check_regression/results.regressions | 26 ++ 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 26 ++ sumfiles/g++.log.xz | Bin 2630904 -> 2652504 bytes sumfiles/gcc.log.xz | Bin 2222728 -> 2212516 bytes sumfiles/gcc.sum | 6 +- sumfiles/gfortran.log.xz | Bin 893672 -> 894352 bytes sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217104 -> 216960 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438192 -> 445080 bytes sumfiles/libstdc++.sum | 34 +-- 39 files changed, 223 insertions(+), 558 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions