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 071f9fe81c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 2aecdab5d0 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 62c1c20679 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 0d5deabaf6 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards b2d581b648 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards b64ca4a460 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 48affeb78e 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 58080615ee 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 6bb117065b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 0b7b6173e9 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 6fa36010b1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 13fbe50d93 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 3763506211 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 60af5076d1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 0321d1f524 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 19b0772c0e 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards a200b51305 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2e2fac2d3f 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 344dc2f1ba 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards a2b5be8550 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 2535232b84 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1e425354e5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 3b7c16890a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 143378cd8e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards c032eb24a7 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 09c558d64d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 454c317925 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 70ff120b3d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9dffde6211 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards d1829fcfc2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 89663073eb 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 094eefa034 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 60db054673 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 9c200b6df8 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1a404845bf 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 62a33d02a1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards ca56548d27 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards f906d2a6d0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 9d1e986f3f 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards dc6e260328 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 93883717a1 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8967f46214 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 4990eca4c7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 64ffaf4331 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0d8a8dd038 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 7b209f6ef0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 85579b6d98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 874646175d 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 9a8e82ac75 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f469bf2fa7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 0b54db629b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards dbea7713ad 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 39656a5eb4 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 8b02383e8b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards e5a897a0e3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards db9ce9fac7 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5bb2785cdd 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 8d6dff6b8b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards c4bf6412e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 21fae951cd 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 48483804fc 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8deb52e74d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 305a6914d7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards eadf00b3a1 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ede47a6e8d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 6bb1f093cb 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 62d4ed0d59 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7a9f925cca 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 3aae0c1005 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5f653f45a1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 2ae54d8ff6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1295fb9196 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards fa5eef648d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 15c02147ce 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 3db96e734e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards bb54266af7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 23f695fde9 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a72287906d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 16802c5b4d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5ad24e3b3e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3b03645566 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 7fec6691ae 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 41f8984d0c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b51b6fca60 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8b2ff1eccc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c1c6bc72c9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b3a72dcbef 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 752facc15b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cc0406817a 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4066ec7914 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 29aa62165d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 9a4ad1ab5e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8813be423c 75: onsuccess: 1: Successful build after linux: 44 commits discards 03db72c66c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 00ef89321d 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e0e9cd1cb 72: onsuccess: 1: Successful build after linux: 12 commits discards 19d80c21c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards cd14098c1b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dcdfd99573 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 303e370a82 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33984b6383 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f0a5f24a44 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8fefcf48b0 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c11a675b2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new c69d6497e3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 242af325d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 8d4ebcfcbf 72: onsuccess: 1: Successful build after linux: 12 commits new 830496133e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 458b65aa96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 39a7e3bee3 75: onsuccess: 1: Successful build after linux: 44 commits new 91ea91fd94 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 01873480a6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 503febccbd 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 484ba5ae18 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ac0152c59d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ed3f60a930 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 848c3a470c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dc7e0d8a98 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 1027e8d691 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e1385db204 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 4fc3690a9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 60e760c285 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 8cc7353f56 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 06b0404741 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 4198919a83 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 798df13a5a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 88e6a82edd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0dd27c0cf8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 7a296ca038 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d91b4de0cc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a455d7d603 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 17930ed0b7 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 3379109346 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ecba86c5c8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 20dd0aeaea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 790dffe978 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 5430c691f6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new fad593599b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b2497a9718 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 51f3228056 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new f0873b63c0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 0ae0b09ded 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new dbb042f0fe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 7478b50a97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2a1e600fa3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 21a3ba8ceb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 3925fed944 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5c85382a78 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3d15d1822f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c0fa9f1f50 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 3e5bf61a7b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 34a0f2a046 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new b3ffa4d7df 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 329cb6c5f3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 728be28c77 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 50925b503f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new df2b71fac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0435bca341 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 6769d555f0 124: onsuccess: #2159: 1: Success after linux: 23 commits new 6877f7a418 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new fc2699cfa2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 0dd86766a7 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 7fb40cc54c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 809b3241c6 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2ea701dd33 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 875c9ef0d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 8514d48403 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 5680f760e8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new e79832f07f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a9c378a4aa 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3419c2bbf7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new c95358486e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5e45b6d5f9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 2a7f3babad 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 851981a1fc 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b7ed1a9a2f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 3605df8610 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5088c378cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 5f8b71c40a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 163fffdc8e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ea4f9d04d6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new e6448de526 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 6bd3f33ae2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 77b8765cee 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new d9070cfc69 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 3f332cd4c5 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 1edf1366c0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new ac91615e37 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new b7f7f4a43d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 4d9f7af32d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new db3c83745b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 4b6ea9ac2a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 83c7b85621 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 99bef2312a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new b6153acd4f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new c2765a2fb5 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 1e993eed7b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 777eaffdd2 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 5006cb03e1 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 69a39416ea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 7ac3f867b8 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 853e7c7717 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e18d6daa24 168: onsuccess: #2203: 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 (071f9fe81c) \ 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 1700 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30540 -> 30136 bytes 04-build_abe-stage1/console.log.xz | Bin 72488 -> 72176 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9536 -> 9468 bytes 07-build_abe-glibc/console.log.xz | Bin 239692 -> 240004 bytes 08-build_abe-stage2/console.log.xz | Bin 204848 -> 202628 bytes 09-build_abe-gdb/console.log.xz | Bin 37660 -> 37372 bytes 10-build_abe-qemu/console.log.xz | Bin 31428 -> 31792 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2464 bytes 13-check_regression/console.log.xz | Bin 7628 -> 6384 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 11 + 13-check_regression/mail-body.txt | 82 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 314 +-- 13-check_regression/results.regressions | 31 + 14-update_baseline/console.log | 38 +- 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 | 84 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 31 + sumfiles/g++.log.xz | Bin 3417424 -> 3443748 bytes sumfiles/g++.sum | 185 +- sumfiles/gcc.log.xz | Bin 3023120 -> 3017360 bytes sumfiles/gcc.sum | 3956 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028440 -> 1032696 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202268 -> 202740 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422452 -> 424924 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 2347 insertions(+), 2569 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