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 09a90c7a19 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 219ecf6193 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 1c9632acd5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 6bd9c11869 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards f7dd916bde 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards bb5f972446 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 0f8f4f90b8 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards d5f9178ff3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards b5cb0c3b38 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4f9a41a02a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards df9d296ecc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d9a9ae2327 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards d58a225156 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 695822fa4d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 45be54458e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 44a59c1ea8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards d57ed27d5f 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 4e97d31ae2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 657b5b86ff 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 99fc7f2747 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 81a8c73017 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 366df3c371 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 30ccbe387c 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards bcc57c1a71 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 8cd3807159 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 9fb2f7e845 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 6ea33c90ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a334cc3e11 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 4893df2904 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 5ebae0cd2f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 0473c9d58b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8d3bb40aa5 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 6eff09d291 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards a0151ef016 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards a6dfca3a13 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 240e2a9e2a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 1e5d2a90bf 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 7f21ef59f0 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 6cbdd0af8d 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards c02baa5a29 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards a86e67eece 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards cce79914e2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 3abdb97d8f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 82284034e4 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 42ebe8cd0c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 1c9cd15b22 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards fb3cae3c04 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e668850c56 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 2374b3cef5 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c6dce44d09 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards f4c561485f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ebedb15690 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b6d0c88d83 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards bbf28d7cf9 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 88ba81a12f 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cc071d6a5d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2d929928f3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b4348ee022 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 5659332784 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 2901dfbcd0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards a97c104988 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 44c2c6c54a 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 242c844469 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 392e0c6ace 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards c3801e011b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 77f8ee9db9 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards f181a7b269 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 0770c9d1bd 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards dbd662ebef 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 16d137e8f4 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 56e0250776 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d8d60333fd 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6348aeb18d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b41ddaae15 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards f0de05a207 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 3bd0801eb9 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 90056a6f46 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c8f9e47786 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards b20aa17f04 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7ce1012604 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 7931e8d143 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 3cd60ba346 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fca892706c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards f1e37afc31 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 3bac096485 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards b2ed72f214 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards f2039251e3 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards be54683335 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 1e837c9729 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 4ebafde2a2 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 78509f90f9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 4a4e5099a7 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards ed10c486dc 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards a3a4fe688d 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards e90a7d9ebd 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 09af4c7227 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 90b43e42fe 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 198fe99af0 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1e900643cf 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards e2b37e351c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 760c3681bb 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new de2b64e92e 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new f57f68a532 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 6c0f18319b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 9bae38121c 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new a04ed0f392 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new bdcfe4c698 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 9087d5541c 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 9341d44105 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new c457627a2c 290: onsuccess: #2106: 1: Success after gcc: 2 commits new db4b68b55f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 5bb40a8c8a 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 46d53dec66 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new b65c378448 294: onsuccess: #2110: 1: Success after gcc: 17 commits new c3f5a52e78 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b1498f7966 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 9cc350bace 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new d9c83a9c70 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 0958319a52 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 0d86d73a93 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 8691656182 301: onsuccess: #2118: 1: Success after linux: 16 commits new b44c20fd68 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 10b813ba9e 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ebfff66aa4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 2812c159b1 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new c3db7dbfa6 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 9dc3b04625 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2b98f4f64d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new cd77a3dd81 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6db3b56b16 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 57b6f77663 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 8de17d8286 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 2a1f5beb5a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a774fa0a1b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new f13da0bef1 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new b61659ea68 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 2a68e1164a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 5dd1ce55aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new cc4e611a1e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 0c1158e3fb 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new b42f069df6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f6e83f7425 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 764d836122 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 23836d80fc 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new e356818cf0 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new fa40cdbbe6 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 28663d243a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a23c4626a5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 5ffd4ad7dd 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new da408541fc 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 46d6cf77fe 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 254548b262 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 4b85fbe7e4 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new ebd35086eb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 331d1ff0c2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new ebe0515c86 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a9b14cca65 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 20b744e83f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 13ad65a6bb 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 63bd8aeadb 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 59cb80676d 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 995b0784f8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 3d75f8f2f3 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new d29ce4831c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 452c4bedd4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 484044be39 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new d50045b383 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7f00efcd42 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new aa68006432 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 63167d18ed 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 8ea41eb7dc 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7ff8dee039 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 73370bdde0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 52d949f1f6 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ab6993079e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new fcf14fa59c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 41c3a0d8b9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 87c0fa8848 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 40c7b0097f 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 05ad64d785 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 26f843c42f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 81f1b8762b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 357a696d73 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 961ca1f8bb 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e9c48877ad 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9e6f72826d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 7af0a0c916 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 63c1abdd5b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 5e84a3f12f 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 4bbed26d81 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 6a63eced2c 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8e4539772a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 45728d1657 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new dabf98eebd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new eb30ee5371 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 8eedcb7b4a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new d18be013b5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 6f38262115 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 3c18d14d54 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 0ab635350d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new e5313653bc 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 5955e40629 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9ffae6ef7a 383: onsuccess: #2204: 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 (09a90c7a19) \ 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 1848 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30888 -> 31020 bytes 04-build_abe-stage1/console.log.xz | Bin 91388 -> 91756 bytes 06-build_abe-linux/console.log.xz | Bin 9008 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 236844 -> 236748 bytes 08-build_abe-stage2/console.log.xz | Bin 227972 -> 228180 bytes 09-build_abe-gdb/console.log.xz | Bin 38148 -> 38164 bytes 10-build_abe-qemu/console.log.xz | Bin 31728 -> 31976 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2644 bytes 13-check_regression/console.log.xz | Bin 5760 -> 6184 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 45 +- 13-check_regression/results.regressions | 30 - 14-update_baseline/console.log | 42 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 30 - sumfiles/g++.log.xz | Bin 2638756 -> 2632892 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2189016 -> 2201944 bytes sumfiles/gcc.sum | 2208 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 888844 -> 895796 bytes sumfiles/gfortran.sum | 11 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214556 -> 214480 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438592 -> 435872 bytes sumfiles/libstdc++.sum | 31 +- 43 files changed, 1274 insertions(+), 1325 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions