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-aarch64 in repository toolchain/ci/base-artifacts.
discards 83c61381e9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 1b2eaeb7b6 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 94e9c2f22a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 65b5c74072 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards dfa55e8a3d 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards e34af2ea60 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards b187baf80a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards bb06ee14a7 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards eb43d75450 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards d2904e58cf 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards f7be9f316b 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards dd38200e5a 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 7304efb6c2 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 10e247bb3e 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 18f77e8e64 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards f27f65e505 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 275a4bb3d6 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards b903f2c5f5 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 8f7bfe0542 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 4ea123ab77 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 950e78d22b 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 64a5a83120 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 4c7ccf2175 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards c4f7b8128a 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 90d2825951 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 5356fe94ce 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 17b231b048 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 02ff49c743 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards b121d0b845 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 4b194d9c86 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards f0e7cf55d9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards e4783ce991 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 7ae525730e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards dc9a574bae 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards ef34624ead 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 434e77d749 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 520e1f5725 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 531a4874ac 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 13527b774f 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 3868dadd86 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 8ded6f2c52 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 7a8ffdce5e 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 7833052b1e 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1c4764458b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards abc518312e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 4a2c1f04d7 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ff0907a7a0 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 01cf50172f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 02441b93e0 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 9c93acd1bb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 193e462515 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 5f7d6758d7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 7b0a82d9b2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards cd54789c6c 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3c900a4cfb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 0c9a09398d 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 14f0fbc30d 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 73cfc488f7 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 530bc5acd7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards b65a49c79a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 028e137268 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 668951a4e5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 1c1519dbb6 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 36d6e8a119 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 86b04f53da 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 1cadeab843 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b3dace8624 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 86397927e6 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards cdcca29149 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 24384a7dae 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 4842c9c087 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards e94235ec61 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1016096244 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 056de0dce5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 392eb63913 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards d1fd2725eb 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 3917d89028 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards f7ca19dd02 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards aebfcfaeb8 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4361d24e4d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 87e848d951 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards ca687d20cf 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 2196dd20b3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 39ba68237b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards b4fa52722b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 19cd14ac69 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8af20e2663 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e379519de7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7bf83fc2d5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards dccaafc252 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 8e63b40a24 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards a3699b693f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 849e26beea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 19c156dbd8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c6466221b1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 2171b46134 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 0c4e8980ad 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 552a960c83 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 330f9881cc 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c907ea4ac6 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e477b4a07a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0187e6b564 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 5a24d76f6b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 61a779d20e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new fc5a4e2c20 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a79c042405 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 386f82ed8a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 4770c8bfb5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 8947d53f9e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7aeff9038a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 108206a489 101: onsuccess: #2130: 1: Success after binutils: 81 commits new bddd5f8785 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new c00d740c32 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7067c3972a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 19b992c80f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 516a835ae5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 3410f51e46 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new c6db8642b4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new ae777dd555 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 75550544ee 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5c01c1970e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 53c70e9258 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 24d91215f3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1de0a42ead 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 90f3182295 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new ed2c1133ae 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 1622418dc8 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 627a151141 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0f511ba32f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b67237007b 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 46d5666e27 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3af108d6a0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 5fee9a8957 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 855ccddc7f 124: onsuccess: #2159: 1: Success after linux: 23 commits new 94f704c653 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8439fc6b36 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new c1a8dad8d8 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 90becd5c61 128: onsuccess: #2163: 1: Success after linux: 23 commits new 44f4fb0325 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 37a7fbef90 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 14061aa512 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new d6c4896a4c 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 092f1a1c39 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 2bee8f0951 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 7fc75af66f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 2b65f82672 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new c9c10799fe 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2c6dc70d9f 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 1d51486a7b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new c341c931a5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 9a38db983a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new f110a27726 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 24ddee93a6 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new fed789e456 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new d67f97dbdc 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 67e755ea25 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 223901ed62 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 802130f1c2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new aadc046e4a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b4ea912079 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 8d8bc237b1 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 9c3957815a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 6e521d031b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 1d22e9a17d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 465272ebf8 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new c064883a7c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new e3bb3c497e 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 57fe97d57d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 5195c3adf4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 7cf3fdd68b 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 85d9a38222 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new c521a83b8e 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 4c4f50118b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 2f9da0337a 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 0ce8aa758e 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new a3f5715aa5 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new ee0cca6e60 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 2058f520a1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 7959a30f30 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 4356bfd0c6 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 27e96cc003 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 992c445efe 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b9d3203d45 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 15d08bbacb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new a1201e1fcd 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new ae832371b0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 9fc564c8e8 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new e1a3442e68 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6e346a9c27 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 5b8f1ddb91 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new adcc3d85c0 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new bf92d9f200 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 6fbbbe0f52 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new d515377c39 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 262959bf2b 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 3c85ae14ae 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 111e6950f7 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new ecbdeaef7e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 7ccd35732a 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 250b750318 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 0f8230ca97 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 0d84b6cf55 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 47cac71511 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/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 (83c61381e9) \ 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 1728 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30772 -> 30896 bytes 04-build_abe-stage1/console.log.xz | Bin 71964 -> 71488 bytes 06-build_abe-linux/console.log.xz | Bin 8868 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 244488 -> 244076 bytes 08-build_abe-stage2/console.log.xz | Bin 203060 -> 202632 bytes 09-build_abe-gdb/console.log.xz | Bin 38108 -> 38208 bytes 10-build_abe-qemu/console.log.xz | Bin 31808 -> 31352 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2724 bytes 13-check_regression/console.log.xz | Bin 21892 -> 19204 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 404 -- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 2157 +++++---- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 101 - sumfiles/g++.log.xz | Bin 3430724 -> 3424068 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3022616 -> 3048356 bytes sumfiles/gcc.sum | 7575 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032356 -> 1034216 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213660 -> 213500 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422840 -> 427608 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 4964 insertions(+), 5863 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