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 9266bb9237 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards c1c56b9012 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 23f59eba11 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 73dd4a3d4b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 4fb2ac06d5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 58a5b2b2da 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5436fa58e5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 89209e7f07 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 62b49de642 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 34b646d3e3 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 006a32574c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 621f9eddaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0d2ce2868f 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 00b602ffbc 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 7bb6e334db 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 2e0592fd8b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards b6cd850423 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 95a93b6acf 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6f301045de 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 3353050a65 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1e8154bc13 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1791e53f4e 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 0774ffe7a9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards b2eede7b4e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 7700c58c46 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards be35bd6b0e 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 15858c7411 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 85d2ce6cde 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards d8e8dc4ad6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 881dee4049 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 7ddaaba8db 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 293f77eca9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 7e967ea171 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 08eff115e7 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 43fcde4877 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 903cc3ded2 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 9cf5943abb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards dbd26104af 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 1f5304bb82 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 8b198673a7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 85600fee9e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 57e1e4fe9d 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards ba7761119c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 4f5da5d4e7 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 6340e5b359 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 2e96daeefc 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 1c029b60bf 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 23dd1bfc24 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 778009044b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 5b3f930434 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 9d5d56ccc7 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards bf58b78d10 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 541912f36c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 27e02f3659 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 90a8de08cf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards a7f6cb800e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards bcdc712f67 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards f16fc3a7af 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 139bdeddae 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards b355fa1d39 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards f366a18668 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards f1c80ac746 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 5d8962cc6d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 61a5c60339 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards aeb44f8c0b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards cf20b01f53 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards c466d6b5de 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 379f311e8b 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards fe9b3d8920 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 9843a25626 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards a3eb0375ca 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 49d8f549e4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards de596fa09d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 0774e468c1 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards c6ee954d07 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 74800c6304 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 4d3e7ca6ab 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 3e04b4886f 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 6a0d4f0b8f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards d09e12fe12 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 77cbb60cfb 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards bdbe6bd119 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 85b8b33497 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 72fb18f872 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 73a6e0e2f9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards a0e9141722 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 177e30f788 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 4f09fec9e9 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards cfa292190b 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards d93f3e93e6 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards a1e92deae3 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 8f1db6120b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards dcacea044c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards eec4882010 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b0372c8893 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 453748c11c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 84863c0ca2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 881459eace 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards abd685a435 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards a71e7ecb2e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 23793002ee 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 89274e641d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 52a1cbad90 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 11852a12c2 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 64410c3bde 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 19d772eab5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new a01a4fdab4 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new b6f2855b45 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 75c0d28c58 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 2495d57536 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 738bf38854 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 1b5aa624ce 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 9fdeb0cb33 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 9faa01ad78 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 133219599d 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 6f76c017bf 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 4a355a5d41 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 42dd12a482 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 4ab1fbd6b7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 83232dccf8 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new cb33236477 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 58972c7ed2 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 3434ce2d79 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 3af9bf8ead 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b9e8ce708d 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 280f0a1a1d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 651e632e73 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c18dc8ba87 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 4ebbda8b27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new b4f41144c6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 0bfcf641c4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new e1a110b5ed 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 5247a8ce3f 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 3e9294274e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new db56c8a440 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 1c7f2137e9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new e2cf38f5fa 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 2aa75b111a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 0125d0c3ad 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 599a8003c7 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2ce056c808 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 4720589aea 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new feacbeaafd 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 5d84bf8eb2 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new e285c63fc6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 2d072d9cf7 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 4cbf720f24 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 180e8ae531 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e298dd5e06 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 289212b115 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new df48415f00 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new d27b48926a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 9ea3885c2a 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6e5e944965 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new e1b4b39fc5 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 0480dc8229 290: onsuccess: #2106: 1: Success after gcc: 2 commits new dd8062c907 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new f961f1ede0 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 9fc3f28305 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 26a0ee1ee3 294: onsuccess: #2110: 1: Success after gcc: 17 commits new f6af0b5f32 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 1e58877606 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 9db98da9fe 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new ed98ab7c9a 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b14f60e80a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 344d0e83cb 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new df357a5804 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5dc958c0e4 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 79881cb236 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 231b7e0b0a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 1ebbcfd335 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 626c09a700 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new f8d9b4c6b5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new db33f9b7f0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 785a8080bf 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c7760d663a 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 0ccc744dc2 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 2247aa0421 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 037300bc89 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a7b4b81134 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4ce7196d07 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 4369399ce2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new cdd7f3546f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 1e37b1af8c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 5def288e1d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 6a101f636b 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 2baa929582 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new ff1dfe811b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 55077c694d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new ba924830f9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0cfa2975fe 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f6f7d15033 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c3d7915116 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 09acfbccc4 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new aa1df27003 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new c27e4e50e0 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7e7b8691ff 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 130d146fe8 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new baa4e9f026 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e85c42ee6f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5adf4c6905 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 90c1861e7a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 382db71281 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/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 (9266bb9237) \ 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 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32196 -> 31868 bytes 04-build_abe-stage1/console.log.xz | Bin 92460 -> 92112 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 238432 -> 236052 bytes 08-build_abe-stage2/console.log.xz | Bin 231468 -> 227920 bytes 09-build_abe-gdb/console.log.xz | Bin 39764 -> 39376 bytes 10-build_abe-qemu/console.log.xz | Bin 31708 -> 31172 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 3224 bytes 13-check_regression/console.log.xz | Bin 6376 -> 6364 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 | 21 +- 13-check_regression/results.compare2 | 41 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 26 + sumfiles/g++.log.xz | Bin 2665288 -> 2690728 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2267784 -> 2226068 bytes sumfiles/gcc.sum | 2359 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 895804 -> 892088 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214024 -> 214172 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439012 -> 432284 bytes sumfiles/libstdc++.sum | 2 +- 43 files changed, 1414 insertions(+), 1276 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