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 5ed8c8f84a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 8f5762ce52 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 212ebfa628 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards ba2f0b497d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 871b2ad895 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 6a44a73866 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3b7507fe54 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c1242a4b61 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards eb57f4aee9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ef862923ad 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 446b82b996 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 2cfeced858 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c5d6cf1c6f 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards acd860c1b5 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards fbf79af517 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 8c720b4c10 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 45f524af95 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards ffb679607a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 036a194149 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 47e7d4d732 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6c053a30f9 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 73c814794d 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a6e83eb974 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 94029d8c2a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3afcabf502 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ee2cfcf353 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 75b0be8caf 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 8e537b408a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 69c4c9f878 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 095d57061c 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 14feda12fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ca62db852c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards ecaf6bac24 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards e2d9d00b4c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c24d15a2a8 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 06b426a18e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards f51a3cd06e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 66b986221e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 2fb5fec800 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards b06936d167 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 7572a2f539 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 0ea6b83516 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 7a9f4b67b6 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards c653549660 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards c41f7ee138 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 28dd981da9 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d6345e138a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 7cd03278d9 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 872aec64a0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0a216c66e9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards d68773a8bd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards c524e2b940 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7002e3905b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards dbfb71c569 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 8a073f52ef 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 3cc4849e4a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 91643b978d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 017d7f4098 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards c1c99aea39 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards a31b3b9174 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 3ee1c088e6 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 6932883502 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards d0d93375fa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards c84d580c9c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 66412e399d 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards aee4b95b3d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 756b618f7f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5df2426b64 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1dbe17322f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards af08aa29eb 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 85efb93ee5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 403f154324 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f3db47d97c 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 18325b2682 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards f9b6af128b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards a1fac288a3 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards e4ba875f5b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 1c92089965 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 1a3419e330 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 70840a5365 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 04a91d34a5 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards ff9e6a2ada 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 9be7e0f681 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 57e3e21ae0 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards ade1df0bb8 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 2c5efab7bd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ff2a62dcf8 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 89ec3e5e4b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards f83e88dbfa 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards eddbaa1917 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 4d71d12552 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 10b5a9ac26 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards c5302b9616 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards a1c5fae8b7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards b1fb2f203d 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards c1a35c2744 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards e00e74c5e0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 695787351f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 3b997c3087 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 73a93461fa 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards cd657d5b67 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 905877e942 232: onsuccess: #2048: 1: Success after glibc: 2 commits new f8285c2808 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 9067c7955b 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new edac5765d8 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a7f715be50 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new a38e19056b 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 004eb159aa 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 2a1479e0db 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0f034136d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new de5a99844b 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 099193d5ad 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new fd5357a35f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 432552691c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 8aab6b6289 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 465cc5919e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new f8704c1f0d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 3405a19338 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new ff3741e38f 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 68d881ea64 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 4c132d5f77 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 68c4d13002 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cfdf888181 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 0fae75659a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 012becb5ca 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 012265c79d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6d1110d474 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 5425da1f0e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f2326bf861 259: onsuccess: #2075: 1: Success after glibc: 2 commits new a5220cee5e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new a0c349b424 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5f8c0f4128 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new e1cdf564fa 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new e5520413d1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 25f776dbcd 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new c06e61b0b0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new d8f34ff0f0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new a6f9892134 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new eaf3da2d32 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new dc1b764ee1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 4101ea38f9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new b45709bc58 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 3cda9abcc5 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new f94f9a1ab2 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 54f143fffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new e6b6937a0b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7a68f66647 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new d059746c2b 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d07a0343a6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 58897fa6d9 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 80b5215ded 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 37a57e938c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 5d5a2ea797 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 87a096c4a4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 84cb40823e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 93ff829810 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 83385cfd51 287: onsuccess: #2103: 1: Success after gcc: 9 commits new fdf7b2c944 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f9957f9dbd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 853cc30d7d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 6687cc8d75 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 7eac67c17e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new bc9a7cd934 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new ea7f0f780c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4c5f5f93ec 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 12c4d31657 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new e0e776ebc9 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new e4868502cd 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 702d49a0a0 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 48f13a2495 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ad32bd0011 301: onsuccess: #2118: 1: Success after linux: 16 commits new 0d145e2035 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 4a47c53363 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new fab9ffa6a0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 1f0a1ca065 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a5b96de83a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c5a41b8c4c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f41011dd23 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 1c0d678b53 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new d5c7129ffc 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3831295f99 311: onsuccess: #2130: 1: Success after gcc: 4 commits new abab2a34e4 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 6ea18c4e11 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 66e6ed057f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 43709a6d43 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new bdf66e48aa 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 8d73cb6c10 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new bdd8e82eff 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f1226b1e0b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e98433c259 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e02cf5b6a5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new db35fee8f6 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 05a8cf86bd 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new db39088e15 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 3f346df29e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f934e6e439 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 55b134b20a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 0fcf68bce0 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new ed504dd967 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 67f5f69fed 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 007db34804 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 06acba9d12 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 735ed65148 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...]
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 (5ed8c8f84a) \ 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 1768 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32124 -> 31912 bytes 04-build_abe-stage1/console.log.xz | Bin 92512 -> 91488 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 236600 -> 235652 bytes 08-build_abe-stage2/console.log.xz | Bin 229240 -> 228624 bytes 09-build_abe-gdb/console.log.xz | Bin 39500 -> 39484 bytes 10-build_abe-qemu/console.log.xz | Bin 31312 -> 31196 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3316 -> 2492 bytes 13-check_regression/console.log.xz | Bin 7084 -> 6192 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 15 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 35 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 35 - sumfiles/g++.log.xz | Bin 2690160 -> 2690552 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2237352 -> 2245440 bytes sumfiles/gcc.sum | 2322 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894608 -> 900076 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214112 -> 214076 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435940 -> 444200 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1306 insertions(+), 1417 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