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 6c824d0be8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d3aa0aff71 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 5f1eee3bb1 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b971f3ee16 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c3f2bdd5a9 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4fc759d844 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 908e4f8365 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards e640cb5e7a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 06068cc790 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards d86a0ed08e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 0fafa31435 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 45e9763f9f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 42e8a2a21e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9b0e81c44c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 710bf20501 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 4c20a69357 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards a3414f91f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards ec95fbaad4 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a88b20a031 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 4e731c8ef5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0178ea85ce 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c9cc1f65dc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9f06019dde 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards d0d34be69d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 7380a5dc2c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 9d84a3ce34 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 98a70bc5b9 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards d161c5ad31 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 14b2a02587 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d4d26e1972 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 3a18a06bf3 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 598e69c54e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 004dc3657f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 08fd32f261 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b582291c4b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 2dd6acb727 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6f6c621aa7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 24266699dd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards ba02b6fe2b 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards cae459a612 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards cd8cfeddbb 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 886ff12250 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 338be4d515 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards fca4a7e170 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 89e74b3b20 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8adb8d613a 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b2c29babe4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3cc8fdc28c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 7b9f3b6d32 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 4de9a44ae9 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 958e452f0f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9b22c49b19 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 54d8a3325f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 47140889a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 59208a00ab 301: onsuccess: #2118: 1: Success after linux: 16 commits discards c21ea91863 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 89886ae647 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards fd8e2288bd 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards d83f16c506 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c7cbc3cb04 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 90c83adfc7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 810cdc2bd7 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 783e97ed8c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards b509f272b9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 08213c04c4 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 88615de8d1 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 21e6ab3768 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 383353bb0b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards f1d9404103 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 053bc4faa7 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 248df88ac6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 61e25423bd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 79e0887708 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 45ead76530 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards cb8bfe0de9 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 203de9c2ab 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 6033e5aad2 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 5edfe816cc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 5ddddca560 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 21d725f40f 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 476e7d4326 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 5109350336 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 3007d850e4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 84fa122204 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 0b1320b33f 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ace9e2f5f8 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 2e86d555a0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 29f248c141 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 5181435569 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a301c1d869 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards bae0955a72 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 9f1188e619 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 9596de9ac1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards bc7a3f1838 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 77df4d521f 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards df6e0e77d9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 84363ca0f0 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 7b139c3d37 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 7033bc42bc 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 6dc390b63e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards d6e50cf927 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new e7fd3b360b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 36156dd843 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6d3ca238e1 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 8590cc01d4 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new c50851331e 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ca72861df3 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new e7e480cd35 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 6336490cc5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 7d66e2076b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 190c786675 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 832c658e13 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new d592c974e0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 1647cdaee5 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 88b154db1e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 72be1fbac9 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 1feba647b6 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 0ea618aacc 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new b3fc3d6b96 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new a4d254dd86 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 194c6b8135 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2d0e118960 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 95d2467d92 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new ccaeb3ec9f 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a35b39c113 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 06db67a1f5 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new b9841c769f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new eb880c40fc 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 37b98fe011 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 2af30d0864 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a849d15570 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new a63161fc6e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new c2f5bb918d 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 2d201d8e55 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 40ce0776ce 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f737d43236 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new a4dd2a310b 290: onsuccess: #2106: 1: Success after gcc: 2 commits new ff991b4cb6 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 0d1bf1871f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new f94fccc739 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 5ac5035593 294: onsuccess: #2110: 1: Success after gcc: 17 commits new fbeafd8f5d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 37d8531fd4 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4b874580f9 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new a277f40d90 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 939615e23d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new b100233e08 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ed9a524b16 301: onsuccess: #2118: 1: Success after linux: 16 commits new 15d850accf 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 53719cd45f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new be03c32fba 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new d360428b7b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 569595e342 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new f426d23097 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 88223687f5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 0086b8ed91 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 6428c1ef18 310: onsuccess: #2129: 1: Success after binutils: 4 commits new dcf4b391c1 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 0fc63d5965 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 3bcceddf9d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new c15f4158cc 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 0f7d98f22a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 5a8a7d362b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 7ca6603d94 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 463eff45ea 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 045bd3f208 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 9e939e4290 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 20c6cc8afa 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f5de9f78ac 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0d28e2e29e 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 3930a5f46e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 075688961b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 77bc296916 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new aa06529664 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 7cae67449c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 02f24bd0d0 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 30e98715d4 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 3f0036490e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 23a9653db6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new f843837349 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 8879d845f6 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new bae9b98975 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 0b33db92e4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 75726eee03 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 69f37d5da2 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 145e588967 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 7e025224c7 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 173a417c69 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 2a1704f5d9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 42cbe1597b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3e7cfee2ca 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 989152de25 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 308178fe13 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8b95ac7b74 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e8ced3cae8 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new b4b9768185 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 291c4f7c2e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new dfb1504ba1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new c7929e818a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new b35e657d36 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new be00d2772f 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 30d3faee89 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new d10f9b38df 356: onsuccess: #2176: 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 (6c824d0be8) \ 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 1816 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31860 -> 31704 bytes 04-build_abe-stage1/console.log.xz | Bin 91356 -> 92864 bytes 06-build_abe-linux/console.log.xz | Bin 8348 -> 9008 bytes 07-build_abe-glibc/console.log.xz | Bin 235928 -> 236928 bytes 08-build_abe-stage2/console.log.xz | Bin 227904 -> 227876 bytes 09-build_abe-gdb/console.log.xz | Bin 39072 -> 39072 bytes 10-build_abe-qemu/console.log.xz | Bin 31980 -> 30868 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2472 -> 2516 bytes 13-check_regression/console.log.xz | Bin 6376 -> 18344 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 12 + 13-check_regression/mail-body.txt | 101 + 13-check_regression/results.compare | 2081 +++++++++- 13-check_regression/results.compare2 | 2232 ++++++++++- 13-check_regression/results.regressions | 101 + 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 101 + sumfiles/g++.log.xz | Bin 2676688 -> 2669620 bytes sumfiles/g++.sum | 64 +- sumfiles/gcc.log.xz | Bin 2280396 -> 2246516 bytes sumfiles/gcc.sum | 6353 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 894036 -> 900272 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214120 -> 214020 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436612 -> 444084 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 8045 insertions(+), 3246 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