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 9c0986dbf3 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards fa745d572e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards f8ceb12f85 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4e0b90a191 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards cdb93e7f2c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 53fa614519 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 3b45afc837 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 23058ddc05 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 21634d8b3c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards d1e5c28949 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a616b3eb97 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards dc9a893eae 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards c370aafdf7 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 726b5b2e7c 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards a1c1594b8e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards f2809c1e49 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 8bb1303802 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 215016e107 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards b9f57894aa 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 5e1b00b37a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards db52176f88 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 59e8098dad 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e16299c1f8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c8fe5ef9b1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 432e605567 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 793459b701 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards caad3d413c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 3392e7fecd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 852a39cb94 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 928a8e1e41 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 4908fa1987 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 27296b0e08 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 1960cdefb3 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 05732d0066 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards d0fb160fae 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 7d8d5891a0 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards cce12f9e5b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0de8ffa76c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards b5a0fad1fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f8685f0d8e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 66570240c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 99ab22b28a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6a9a27526a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ed53ad0854 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards beebaf3dcd 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards c1d86045c2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards b1d80441e6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 642cf72e88 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9ce4606eaa 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 8255587d74 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 1932682c18 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 27e31fc002 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 13421508e6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards e7899fe96d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards e86ba8efd5 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards e36333ef18 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 4d824a89c9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 3a384cca1c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards d05c5032aa 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 4a6ce8c28e 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 33d297356b 301: onsuccess: #2118: 1: Success after linux: 16 commits discards d81f8e12bd 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards db31bfb19a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 3b9eec2572 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 02c1cb79a1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 559a0f1af1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards baefbc1e17 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 1fc7a07780 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ecf85aedf3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards c899fbef99 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 086ab55107 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8f89f4f338 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 595aa23508 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards f7cd5e6fb9 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 317be00c5b 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 3b29d379d0 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards fa64e4c699 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 8d76ce7b63 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 75d81c276f 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards ff326ba180 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards af0287ca51 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 6bb3bb838f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 2e7aa6bc0e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 379f896e68 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards dd555a6164 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 0da7b5c0ff 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 6902a72b17 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 8aae2351e3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 5ea153dc22 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards f9cb11620f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 20e1218a61 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 39d73c794c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 2a6a24ee74 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards cb72c8771b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 0d4914546c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 19052820e4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards f633cc3d38 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 40a0f55df4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 4e459ac294 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 68f4a89ab1 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards a4b2b4a160 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 987f8fd136 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ad2f1088e8 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new ac310d360c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 93f4291a76 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 1a01ed97f9 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 70fe8a07e2 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 3ad047af88 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new ea3a5882b1 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 910fda1491 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 3b5532ea17 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 64b7b5e22c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 96683664d4 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 82ad9d3fee 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new d1cea08737 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 9778a320b1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 7f4588d8d9 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 706ef57655 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 8491f947da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 1e3058b9ec 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 7dac83fb71 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 6da0eaf27c 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 954bc5d07c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 14deeeb4af 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new f2c3c11788 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 113cbafcc1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 374b592d11 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 8373e43f0f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 7d05c15c16 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 208ae6d9d4 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 9f7620ae1e 290: onsuccess: #2106: 1: Success after gcc: 2 commits new be7a2e6d50 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 549bc6ea29 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 5e105f982d 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 7d737482c5 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 55f9475753 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 8b371e11fe 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 3dbca187a5 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 6fab1b478b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new fc17a27dee 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new dcb0717fba 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new eb9cc38c66 301: onsuccess: #2118: 1: Success after linux: 16 commits new 781f7e889b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 816b39ecf5 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 73bea9fe20 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 7eff4b567b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 1ec0817092 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new eabca8c748 307: onsuccess: #2124: 1: Success after gcc: 2 commits new d71bea8c9d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new f0906c0f7d 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new dc32113e2d 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 5e92937843 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 25713ce4b2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 79917a5d97 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f42bab325b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 901179aabf 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1d02301729 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 9de19d42d4 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ed739b7eb3 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ec51bf4f53 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 749ea928db 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new f111caa4c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b429f0f0ec 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 51d96109b4 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0bc4e97b0a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0c00bf42ff 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new fde5c1b319 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b98356da29 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 26bb3ecd84 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new cef83a6a82 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 88918dd752 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 3055558f1f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 95255b7cc7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 276d0a9bac 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a767244033 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 24042d064b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new c81d15b795 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new c26d7e7812 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 40d8545ef3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 5250d26317 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new fa0d036f97 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 9bfae5c5dc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d1aea38346 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 00dcfb3797 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 551e3a7f7b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 098eea23af 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 51ac9f8b8d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 2090b1a8e5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 5030245ef9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 40a270d776 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new d65c97313f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new c569eef104 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 9d462d3e15 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a061bc08c4 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new c5ce3b5159 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 9aeb87852b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 10be443e2e 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2240252ece 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 01652a6d79 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new cdb25412de 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new e8ccfb51c6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a9ebffa28c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new b05293c3c4 362: onsuccess: #2182: 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 (9c0986dbf3) \ 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 1808 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 30976 -> 31176 bytes 04-build_abe-stage1/console.log.xz | Bin 91940 -> 92272 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8788 bytes 07-build_abe-glibc/console.log.xz | Bin 236228 -> 238900 bytes 08-build_abe-stage2/console.log.xz | Bin 229412 -> 230488 bytes 09-build_abe-gdb/console.log.xz | Bin 38192 -> 38880 bytes 10-build_abe-qemu/console.log.xz | Bin 31960 -> 32012 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2540 bytes 13-check_regression/console.log.xz | Bin 7204 -> 7580 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 44 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 71 +- 13-check_regression/results.regressions | 44 + 14-update_baseline/console.log | 66 +- 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 | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 44 + sumfiles/g++.log.xz | Bin 2636952 -> 2669436 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2213260 -> 2206104 bytes sumfiles/gcc.sum | 2292 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892124 -> 888164 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214252 -> 214028 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434576 -> 431312 bytes sumfiles/libstdc++.sum | 37 +- 44 files changed, 1477 insertions(+), 1285 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