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 5aa33b93f2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 8dee47c368 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards e6b2c8f433 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards cd46eaa96b 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 793c5fddca 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 771fe2d570 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 5dafd9f2dc 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f082e5f32f 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 27c8e07aeb 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards c2af415fc0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards aeab30de29 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 0992c24eda 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 22f14fe993 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 635a4cb077 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 35c096960e 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards a9565436c3 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a9ef5ed833 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards ee575c6a21 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 32794bee64 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards b4d9d1b1e2 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e69b29d566 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 62cf2b14c7 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards c1cc0ba3c9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 12d4542e3e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 9056ae58c5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 21e94162e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 50e169ce32 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards bf04cb79bd 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 5cccfc95e7 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f81f15244f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 0c4af1df5d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards e101c5b4ed 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 6533d6f684 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 1a65a4adb8 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 43f7ecf29d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 684e5b6e7e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 891915d279 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5c10b33e46 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 4cfc004e55 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 51e5f0f5a3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 1d563aaf76 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 4846eb7be5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 27f73b6a2f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3eab5e328a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 87332a3fae 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 35d67d3559 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 29e8cd68c7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 5b0147c7ab 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 016b704fb8 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 106b8cd52a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards e5bd8f9e5c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 9de6ad7f2c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 8204652404 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a7af6c2dbd 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards dbf44b48a2 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards f21cbb86e6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3ceb6bfdba 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 9108e50d52 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 56385ffd96 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 5e8e6279b6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 6c3c28c5c9 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 558e5a8bc7 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 436b0a127e 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 54fa6fb85c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 7c42d8034b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 953e02609a 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 5316b55082 301: onsuccess: #2118: 1: Success after linux: 16 commits discards cf245368f2 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards eff8a93954 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards af8811b6cb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 91960f0d6b 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 62dab02d95 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c97fd8dee4 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards b3d78d603e 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards dd136d6a2b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 055e96bece 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards b61cd5a655 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards a2f97580bc 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 263c314052 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards f2240c5be2 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards c31179c2fe 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards c38088b72c 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 8171a02c05 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 81b6e76c14 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0117f1b6c0 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards a59b9f207a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 144352ea2d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 9ab86350e4 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards e8a27c8b92 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards c4e0be8dd4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards d83da1df05 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 8abe9a50c3 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 7592858483 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 87459c4178 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards e1ad743584 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards f3e0bb708e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 65dec79680 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards c52b3170f7 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards e875e4bd4c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 0da6731fbb 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b99c1b4033 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 21319dfae4 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 675845bd69 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 55f847a243 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 5495e8df23 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 01bbfa4891 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new d8fccf89eb 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new cbc8d06352 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new e6c7c7f314 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 41e7c09263 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 8847052285 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 58b13f4142 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 817c4721e7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 0d9539bc57 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new dfe6cc4e35 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 6483135d9e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 2c83a378ad 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 8b220bfee5 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 6ff6741bf4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 4fa9b1c1d3 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 777557ec30 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 68aebc541a 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 0321247923 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new d656dd4775 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 2b9db276b9 290: onsuccess: #2106: 1: Success after gcc: 2 commits new fc3d81c492 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e527ca011c 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new b3704241f7 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 5fd8e757d4 294: onsuccess: #2110: 1: Success after gcc: 17 commits new a23cfa48bb 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 164c30dbd8 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 243bc75efa 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 40e9d6c4aa 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new c761b3202f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f3080d9f7f 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ccdf49ec9a 301: onsuccess: #2118: 1: Success after linux: 16 commits new 8e1b559864 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 9973fecf84 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new e36db6dbcd 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 719b3b830b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 33f6d7a77c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 91e7fcd1f5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 029e1f7ee7 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new af033fbec9 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6c3e1c9b10 310: onsuccess: #2129: 1: Success after binutils: 4 commits new e183744093 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 3ca4dbb2ff 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new b0e022683f 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new e7b88a0ded 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 89754085b3 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new bb90da9362 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new b3f18d56b2 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 843e9001d0 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 014993aef0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 37ae58f41c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 6afa517d7a 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new e247315b9b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 364e4aaaf2 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new e98a1040db 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 09c964feaf 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3e3a7ed79a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 7a28c39248 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 5ed9cd1e5b 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 4d10ad59b7 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new ac6a1fd878 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 3c47b62444 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 9fc93aedf5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 2f976293d9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 2e79a4fea3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 819e649e66 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new af61295cd8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new ff35b85226 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c93273078f 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 8ffed55e4c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 84e13ee546 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 969e661d02 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 3caca8429c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 8a106b660d 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3464250209 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 803edfdb2b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new efaab978af 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 875ca9be5d 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 04808b8275 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new fde7124617 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 2b710256cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 0497732a60 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new da3ce9f013 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a45e646da3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 8b74429786 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 564e7b7adf 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new bfd95179d8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 1218bc59c3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new d54e17247f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 7edcc41251 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 3869c35a74 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6680abd622 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new be729ddddb 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 346954cc17 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 0b2de3bf25 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 63ae1bdd7f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 3ce733d783 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 0c83bd26f1 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 99391e40ea 368: onsuccess: #2188: 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 (5aa33b93f2) \ 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 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30800 -> 31360 bytes 04-build_abe-stage1/console.log.xz | Bin 91424 -> 92688 bytes 06-build_abe-linux/console.log.xz | Bin 8884 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 236456 -> 237668 bytes 08-build_abe-stage2/console.log.xz | Bin 228088 -> 231180 bytes 09-build_abe-gdb/console.log.xz | Bin 38080 -> 38340 bytes 10-build_abe-qemu/console.log.xz | Bin 30864 -> 31580 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2840 -> 2780 bytes 13-check_regression/console.log.xz | Bin 6908 -> 7804 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 147 +- 13-check_regression/results.compare | 45 +- 13-check_regression/results.compare2 | 208 +-- 13-check_regression/results.regressions | 50 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 149 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 50 + sumfiles/g++.log.xz | Bin 2639288 -> 2643904 bytes sumfiles/g++.sum | 25 +- sumfiles/gcc.log.xz | Bin 2179132 -> 2194372 bytes sumfiles/gcc.sum | 2479 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891520 -> 890556 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214100 -> 214252 bytes sumfiles/libgomp.sum | 15 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433712 -> 436536 bytes sumfiles/libstdc++.sum | 31 +- 44 files changed, 1642 insertions(+), 1697 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