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 5730051ef8 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards e751951428 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 7224520f29 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards c47be7da6c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 757594f9d7 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 6ead0c1802 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d0418474eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards ff1e1f42cc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 03560cb54d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7ea70827dc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards ece08773cf 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 76365fe755 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 90c550d02b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 4f9768ea90 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a130b75a5d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 7c0aa9cf7f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 73c1e5f346 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 957a2b4eb8 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2e54ac205c 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 71e26698b4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 4949f4f7fa 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 71fd849bd0 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5e6248db39 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 6b796cb172 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 3e6e2326a6 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards c17a57e401 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 2feb7bcc55 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a0174804bb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 2d62aa5984 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards e641566c61 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6fe4bd4b75 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 2a6e299461 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9b8e7d3357 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards f601e666aa 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 19ade12fb0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 2f54736582 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards e4b53f1aaa 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 2b7492e36c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 222ce5d2cf 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 7bc8e70a3c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 448f92fef6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 6eb17ad455 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 8dfc42b6c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f7e8e11215 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cb122dd145 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 70041e930a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5fe0743411 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards f5cd689d63 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards aa473eb93d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 4446099b4d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 8705db7dbd 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5779ff90a0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards bfbfd463f0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards a8db67d6bd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c3251414fc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards f686e53b8b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 8ac0299e4b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 6aacce8e84 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 1d6cfb50a0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards ccda61275f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards c0ae260f12 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e4f78463e0 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 690b94b9f4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 7d3b0703bc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 7d8f3830a0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1dd8648e4a 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 537688b0ee 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 787482c853 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 7cf5a77e01 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9bd6fbec2b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards bd1b209548 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards bd61d7b1b7 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 84d2b31de3 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 8895d3ce04 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 86e3e99bb1 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 4270c2a60f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 4e5a4941a7 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 53edd470ee 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards a0073e3fb3 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 5c56d55ae6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 593c0a64cd 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 045e89fef1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 26603dda80 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 96ccd65748 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a6a8734760 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 6b3e33ff52 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 4334d32e0c 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 810adeafeb 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 876641891b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards dd37b22099 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 199ee622c0 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 57ca50d388 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards ea970cfc85 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 7ede9cd3f0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 7cf00488cc 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 95dd9c1ded 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 32eaa453a0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards f9adbeb3bc 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 4c08bd6d86 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards ab9782927f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 182123ac73 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new e946045b0b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 760c3681bb 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e2b37e351c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 1e900643cf 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 198fe99af0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 90b43e42fe 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 09af4c7227 287: onsuccess: #2103: 1: Success after gcc: 9 commits new e90a7d9ebd 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new a3a4fe688d 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ed10c486dc 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 4a4e5099a7 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 78509f90f9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 4ebafde2a2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 1e837c9729 294: onsuccess: #2110: 1: Success after gcc: 17 commits new be54683335 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new f2039251e3 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new b2ed72f214 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 3bac096485 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new f1e37afc31 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new fca892706c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 3cd60ba346 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7931e8d143 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7ce1012604 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new b20aa17f04 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c8f9e47786 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 90056a6f46 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 3bd0801eb9 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f0de05a207 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new b41ddaae15 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6348aeb18d 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d8d60333fd 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 56e0250776 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 16d137e8f4 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new dbd662ebef 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 0770c9d1bd 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new f181a7b269 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 77f8ee9db9 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new c3801e011b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 392e0c6ace 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 242c844469 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 44c2c6c54a 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a97c104988 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2901dfbcd0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 5659332784 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b4348ee022 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2d929928f3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cc071d6a5d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 88ba81a12f 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new bbf28d7cf9 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b6d0c88d83 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ebedb15690 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new f4c561485f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c6dce44d09 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2374b3cef5 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e668850c56 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new fb3cae3c04 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 1c9cd15b22 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 42ebe8cd0c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 82284034e4 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 3abdb97d8f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new cce79914e2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new a86e67eece 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new c02baa5a29 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 6cbdd0af8d 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 7f21ef59f0 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 1e5d2a90bf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 240e2a9e2a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new a6dfca3a13 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new a0151ef016 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 6eff09d291 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 8d3bb40aa5 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 0473c9d58b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5ebae0cd2f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4893df2904 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a334cc3e11 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 6ea33c90ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9fb2f7e845 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 8cd3807159 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new bcc57c1a71 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 30ccbe387c 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 366df3c371 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 81a8c73017 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 99fc7f2747 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 657b5b86ff 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 4e97d31ae2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new d57ed27d5f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 44a59c1ea8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 45be54458e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 695822fa4d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new d58a225156 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new d9a9ae2327 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new df9d296ecc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4f9a41a02a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new b5cb0c3b38 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d5f9178ff3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 0f8f4f90b8 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new bb5f972446 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new f7dd916bde 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 6bd9c11869 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 1c9632acd5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 219ecf6193 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 09a90c7a19 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 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 (5730051ef8) \ 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 1832 -> 1848 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30976 -> 30888 bytes 04-build_abe-stage1/console.log.xz | Bin 91656 -> 91388 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 9008 bytes 07-build_abe-glibc/console.log.xz | Bin 236528 -> 236844 bytes 08-build_abe-stage2/console.log.xz | Bin 228720 -> 227972 bytes 09-build_abe-gdb/console.log.xz | Bin 38264 -> 38148 bytes 10-build_abe-qemu/console.log.xz | Bin 31852 -> 31728 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2692 bytes 13-check_regression/console.log.xz | Bin 5100 -> 5760 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 30 + 13-check_regression/results.compare | 13 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 30 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 30 + sumfiles/g++.log.xz | Bin 2635612 -> 2638756 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2207848 -> 2189016 bytes sumfiles/gcc.sum | 1922 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892704 -> 888844 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214464 -> 214556 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436188 -> 438592 bytes sumfiles/libstdc++.sum | 23 +- 41 files changed, 1223 insertions(+), 1072 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