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 47cac71511 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 0d84b6cf55 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 0f8230ca97 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 250b750318 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 7ccd35732a 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards ecbdeaef7e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 111e6950f7 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 3c85ae14ae 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 262959bf2b 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards d515377c39 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 6fbbbe0f52 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards bf92d9f200 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards adcc3d85c0 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 5b8f1ddb91 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 6e346a9c27 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards e1a3442e68 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 9fc564c8e8 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards ae832371b0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards a1201e1fcd 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 15d08bbacb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards b9d3203d45 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 992c445efe 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 27e96cc003 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 4356bfd0c6 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 7959a30f30 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 2058f520a1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards ee0cca6e60 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards a3f5715aa5 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 0ce8aa758e 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 2f9da0337a 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 4c4f50118b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards c521a83b8e 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 85d9a38222 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 7cf3fdd68b 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 5195c3adf4 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 57fe97d57d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards e3bb3c497e 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards c064883a7c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 465272ebf8 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 1d22e9a17d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 6e521d031b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 9c3957815a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 8d8bc237b1 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards b4ea912079 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards aadc046e4a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 802130f1c2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 223901ed62 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 67e755ea25 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards d67f97dbdc 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards fed789e456 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 24ddee93a6 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards f110a27726 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 9a38db983a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards c341c931a5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1d51486a7b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 2c6dc70d9f 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c9c10799fe 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 2b65f82672 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 7fc75af66f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 2bee8f0951 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 092f1a1c39 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards d6c4896a4c 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 14061aa512 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 37a7fbef90 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 44f4fb0325 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 90becd5c61 128: onsuccess: #2163: 1: Success after linux: 23 commits discards c1a8dad8d8 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8439fc6b36 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 94f704c653 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 855ccddc7f 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 5fee9a8957 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 3af108d6a0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 46d5666e27 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b67237007b 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0f511ba32f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 627a151141 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1622418dc8 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ed2c1133ae 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 90f3182295 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 1de0a42ead 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 24d91215f3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 53c70e9258 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5c01c1970e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 75550544ee 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ae777dd555 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards c6db8642b4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 3410f51e46 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 516a835ae5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 19b992c80f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7067c3972a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards c00d740c32 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards bddd5f8785 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 108206a489 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7aeff9038a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 8947d53f9e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 4770c8bfb5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 386f82ed8a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a79c042405 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards fc5a4e2c20 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 61a779d20e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 5a24d76f6b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 721abef0ae 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f40ae1927d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 5b60c79a3f 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 56b33d4718 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 75eb3e4a1b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new be0d794740 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ab30ef32b2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 1cb30b23d8 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e2a8f4e23b 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e8ab902fa4 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 0fc8e0b7d3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b52378b229 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 034c5627d5 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 20a912e214 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 104643915b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 5ae8c27357 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b761726144 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 6ba57d5494 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 64fe88a5d6 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 5328992e80 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new e876a9e3e2 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9b373419a5 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 696e4d22b6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 009e884d94 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 15bb5877a7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 77a5d556da 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 8621eaf1b8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f590661cbe 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new dfa70e6b5b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new b5109302ca 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d3f0a6e077 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new b5441d9dea 124: onsuccess: #2159: 1: Success after linux: 23 commits new 102b9127c1 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new ccfa525b1a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 11ffa78f87 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 21b7685705 128: onsuccess: #2163: 1: Success after linux: 23 commits new 50bf51f8e7 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5a82e32fbc 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 101dd70ad6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ae6e229e46 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 8dc16d01b0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 5b25a70136 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 7651c2d19c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 65a152a6d9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new d47bdf4592 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 6f96f3ce5c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 1abd351ce1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 376cfa452e 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ae4f3817fd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 8e4429a17d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 47cfb2300a 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new da111a9328 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 0104aa06bb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9602db36e4 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 48205e36de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 9ec63d90b0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new c1af24965c 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ab4bbe8507 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 55dd5d02ce 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 6d2c3b33c9 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 8e5a65d925 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new bc9c0ac962 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 6f46652e93 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 3c1df4d678 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new ec8a8d8309 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new bd49d6be24 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 46c6374989 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 317d076e09 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new a5fe1ce939 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b3819a2c1b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new fd416ef4f7 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 868647e01b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new dcda4d2145 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new cd1e9220af 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new be72573c7f 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e24373d23f 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 7519e4e286 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 178020aaa9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new e3848bf51c 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new bed2e36ecd 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new c26be0a397 173: onsuccess: #2208: 1: Success after gcc: 10 commits new e0f839c067 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 7be9ac3a57 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b07190171c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 1064417e44 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new e52ab5bb2b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new d567df4bc3 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new abcf083357 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new a22d419e87 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 2d4566aa9d 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 64f7fcf5ef 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new fe3a739cf0 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new fd18ec8514 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 1f85b82d2f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new dfa7e38206 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new fab2deb637 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 8cbb817d5e 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 9bcf8a5ce2 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new c0eb63fe52 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 2d97b4bb4b 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 9a9aeea97c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 9a7763a29e 194: onsuccess: #2340: 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 (47cac71511) \ 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 1760 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30896 -> 30440 bytes 04-build_abe-stage1/console.log.xz | Bin 71488 -> 72896 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8872 bytes 07-build_abe-glibc/console.log.xz | Bin 244076 -> 244344 bytes 08-build_abe-stage2/console.log.xz | Bin 202632 -> 204456 bytes 09-build_abe-gdb/console.log.xz | Bin 38208 -> 38896 bytes 10-build_abe-qemu/console.log.xz | Bin 31352 -> 31880 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2724 -> 4140 bytes 13-check_regression/console.log.xz | Bin 19204 -> 7404 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 142 +- 13-check_regression/results.compare | 431 +-- 13-check_regression/results.compare2 | 2805 +----------------- 13-check_regression/results.regressions | 41 + 14-update_baseline/console.log | 64 +- 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 | 144 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 + sumfiles/g++.log.xz | Bin 3424068 -> 3421792 bytes sumfiles/g++.sum | 217 +- sumfiles/gcc.log.xz | Bin 3048356 -> 3049496 bytes sumfiles/gcc.sum | 4791 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034216 -> 1036444 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213500 -> 213572 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427608 -> 433504 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 2912 insertions(+), 5909 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