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 36c89e1d93 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 7ac452cd6a 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 7460576b54 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards b152ad49aa 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards ee33458eee 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards d6a2db3b3e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards c2fb2768b6 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 1a498b9ea3 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b987c162b1 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c377543dd8 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1f7aad88ae 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards ff162d7006 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 525ffff0fe 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards bd0e85c24f 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 798fde396d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 17890ec499 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e4057e2733 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 111fc0f9e6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 239bb5919a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards adca36e8eb 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 74d26debdd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fc819d4a41 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 92891c7ddb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards ecfe1bdb20 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 67430074d1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 4aaba214bf 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 5d8de43feb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f815245ee2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 35fc099774 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 016137e2df 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards d49d5e633d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 1285d7f32f 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 658bf43159 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 115b1b0c38 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f825f01b01 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 3e7c3e8f1a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 791dc1fb34 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards bb8be903ee 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards ce6f8c8ff9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards b7f8705c1a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3808fe44af 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 9bb8338965 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards f2174a946b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6efd54d300 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards c9bafbf688 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 489104d226 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 690fd56d34 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards bad2624dd8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c046be4604 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 3f7f397716 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 8d9bd05012 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards a5fd35b27c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 6479c3ad32 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 63ee3a2382 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 70f00368ac 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 1f4f017217 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f415aa3dc5 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards bd09e6641a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 55c5344738 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5db9d9db21 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 225a501e00 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 79098446a3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 320d2dde9f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e2961469bf 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b0d4cd5fb8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 1f6adb2484 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 8e79577323 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 74927e2c9d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 7ff10f18d9 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards acb45673d7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards dd10ebcae1 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 46bfc2dc05 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 7c40e545e0 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards dffdfb22e6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 1f9769aad9 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e608b70a34 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ebe16b16f9 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 197fac0f06 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 8fe05a28b3 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards ee7064c8db 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards c9dc16407e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2058b150a9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 2e315f7273 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 439510ef54 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards ae8de6e05d 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 61b069cb63 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards cb6dbc7eba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 565e1af7f5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards bd80ea487c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 0918d833cf 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ac9eac4fa1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 8802346f65 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards c5e6f3950e 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 98a509fe10 301: onsuccess: #2118: 1: Success after linux: 16 commits discards ca0618214e 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 3cad6cd796 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards b0a9c19cdb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards fdf1a81cd8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2e8a289015 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards d1b704ed08 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 5ab3d0f2ae 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 71ba2dd5c5 294: onsuccess: #2110: 1: Success after gcc: 17 commits new ced15b4786 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 401797e9b7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f5ed7cf000 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 958f20b886 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 6c82e5eb8c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 61f66db3bc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 35f0559d16 301: onsuccess: #2118: 1: Success after linux: 16 commits new 313e571864 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new d8884ee6e5 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ac2320e2f3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new b91bc1f0ad 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 51029b4b11 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 0d0a8ae14b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 6aa3f0bc3e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 2b33044219 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new d42c502850 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 0a2a2544ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 9d92855324 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9ea4d83aa5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 9898f5f1fb 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 08a01c5e53 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ee088b87c6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new d7aca6ea3c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 84ba18c0f7 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6b60c9c66f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c3b60e8067 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e1bda16b66 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 3f32bf8eca 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new beb534e163 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new bcfa17dc4c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new f4aae1d48d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7441ebef4f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c9b11eb56d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 037c8cb083 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 6db030e5ae 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new daa2c5d96f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e3f330478e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 05c2e8edfe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 07d7784c26 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new d43bd67e7a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 16b0da4fa8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 0489aeafd9 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new ec5bac885d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 5ed96dfda4 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new bb543638f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 872d9c3328 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 7d8800fa46 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new a7877d56a4 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 69c1db87e6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new ef8951b2bf 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 6559c8151c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0380ba805e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e9727e2345 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 052950b40f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 30cb288828 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 3add4cc5d0 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new fa0f28a658 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 12e402e362 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ba3ac232b0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new ec60685ff7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ef039a9724 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 699351e97b 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 6453ff180b 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 5fafc2e891 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new d10c6180f2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new ba7d110a54 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6d8b808e6e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 68199eaaff 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new b433a80d76 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a1eef42ebf 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3604f444fc 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 7536b1a001 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 2f907ca3fc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 31919ce359 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 9ca162168b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 76d2722e40 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new bf14c7dec4 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new ee536b4881 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fe1c350fdf 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3c9e69fac3 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new bae288b59c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new a9cec742a7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 74110b56e3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 5512160d9d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 0a5f81bb71 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 66e10da92d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new fdf1701ba3 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new b244bce66b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 200ce4967d 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 0f32eabacb 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 4800a7a51c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new ecf97162fb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 51a6460513 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 1e7e6aadd4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new baae8f7796 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new b58a98fe71 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e5c6783050 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 8c5f744d4d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 702d00ada5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 5f29bed60f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 17218a2547 395: onsuccess: #2216: 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 (36c89e1d93) \ 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 1756 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31776 -> 31244 bytes 04-build_abe-stage1/console.log.xz | Bin 92844 -> 91500 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 9336 bytes 07-build_abe-glibc/console.log.xz | Bin 237864 -> 235996 bytes 08-build_abe-stage2/console.log.xz | Bin 230756 -> 228236 bytes 09-build_abe-gdb/console.log.xz | Bin 39096 -> 38748 bytes 10-build_abe-qemu/console.log.xz | Bin 32140 -> 30800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 3268 bytes 13-check_regression/console.log.xz | Bin 6280 -> 9284 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 588 +++++++-- 13-check_regression/results.regressions | 26 + 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 26 + sumfiles/g++.log.xz | Bin 2650316 -> 2637436 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2226972 -> 2205296 bytes sumfiles/gcc.sum | 2167 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 895324 -> 888848 bytes sumfiles/gfortran.sum | 15 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214544 -> 216860 bytes sumfiles/libgomp.sum | 439 ++++++- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444944 -> 438968 bytes sumfiles/libstdc++.sum | 32 +- 45 files changed, 2237 insertions(+), 1308 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