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 64ec5ca78f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e591fea4ea 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards e491e77bae 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards eb00cc2d60 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3aad061547 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 276caafa71 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 8c0e2121c0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 1c1455cc4b 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 29d53a2e54 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e104652c31 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 4917f9f824 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards db90266ef3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 4af79fbb2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9fc7a864d0 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards e78355e6f2 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 35160937c2 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 84cf22f6a2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 091473f66e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c304658684 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 17b713e27c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards d02974e9d8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 0238974eb5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 96fbd6a630 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards d97b0a705c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards c606e19332 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 21a22d79ee 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 875a44bfb2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 7e07ccf74f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 68d970f443 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards ccb890a747 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 14ec847cec 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 0ab2d837a6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 5da457b0fd 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards dbf7c8df34 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 7cbdf1f032 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards f217b6e58d 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards d935232ea3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 3aac1d9b6e 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8b27564bac 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 050cd1ff47 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 01f69176c9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards aa340e7613 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 53d821608e 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 1e51bbc37f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1f62cac0c3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards eace8801dc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 45ed7737a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards b610955113 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 6be5776620 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 25025be39a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8f1ca79af4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a8168d6ae7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 8a9fa998df 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 1e01c94ada 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards cbdd69030c 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 4c786c5e47 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 11b0aec9fd 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 69c79dc452 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards d283e2dd0e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards f421c0a998 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 152e956aae 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2057d90ab1 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards aee3670e44 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 98ea183ffd 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c4f83aa6a8 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 24bfe2f708 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 526573222f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards e300175f28 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 8dc5b92a9d 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards f105bc0b35 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 70f5e92afc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 525dff966a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 6063acfd7c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 4f3dce7591 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards ca3b04da81 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 9052abf1d4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards a01680f22a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 37b263af83 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 0e1d0391ad 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 1d09dc1552 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards e7fa75ce24 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards d8ad50e757 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards aa238ed20f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 2d986d684d 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 7983456315 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards f4520e6e8a 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 51ab67b3ab 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards d2bf5379d4 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards c5e2549070 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 34b653d6b2 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 0e79f3305c 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards dca74602ae 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 4ab0fa5721 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards a8e3355632 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 000ee159d9 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 8de2e91baa 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards b2dd9179cb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 8b5e3d3291 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 4ea4427767 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 648bb38f28 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards e7d9cf1ae5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 7505b2c15d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 2fd9b260ac 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 9dc99a4441 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d31abcfee0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new d627dd7344 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 8ed20a5e35 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 462820af19 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new c8712b1519 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new d19fc3bc55 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 1dcb1e424b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new f6102c0704 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 3862e3b6c6 259: onsuccess: #2075: 1: Success after glibc: 2 commits new be684a0fc9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 28e0226f61 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new d94dd717ac 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new d734b45ede 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 8df4e6ef22 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 30e56368fc 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new e7fbd37961 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new a6a27d887b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 01c2cd0fca 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 926aeb8723 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 3ec8a7286b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 72a8c718b4 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 6a357a2e45 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 394367244e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 71a5a876ee 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new d69951e35d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new dbe98a8fa5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new e306a6d8c7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 32f9a92237 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new c7bd0ed8a1 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 1ce510a4f3 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 0c89211a40 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new ab73119400 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 86bd3c8ebf 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 5a0d805356 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 31e2c6e3c1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new fd38ab42fa 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 247db90f1d 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6f4f82e3e0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 0a7d1e2be0 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 26a4e6ddd2 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 39c28c5520 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6afe9e9642 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 78f9d5110b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new f291112883 294: onsuccess: #2110: 1: Success after gcc: 17 commits new f98bea119a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c6409daf69 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 0121d3f470 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 543a4ab697 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new c4b84db67b 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new fd4dac2fe0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 4f29d10bb1 301: onsuccess: #2118: 1: Success after linux: 16 commits new f5bdd5082b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new ac89e41286 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new c2e36059ec 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new db1bfe7515 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 3357eec990 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 35f43c7d01 307: onsuccess: #2124: 1: Success after gcc: 2 commits new afa1fe079b 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 29d79d6542 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c89d13b710 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 7ec6867af2 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 20c7d725cf 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 29bb795365 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 039af5766d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 79bf05a17f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new a480010928 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 4cf4cc614a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new d0e12ceca5 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 27ceb6ebc0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new d9a5b8ff88 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new c01bd30500 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 8ed8492e33 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 28d1e1b740 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 17ea90fa49 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new ecf9ae513f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 201a916d7b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 757a39d751 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new a7624463f3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 198ec8cb03 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 1d04c0c152 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 5802de9d81 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 010ec78741 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 77e255b7fc 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new d711b635ce 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 65cc509c9b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 38ef1d3e6a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 16969a97f4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2858bd965e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 958164699a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new beb7695bb8 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new a399bafbcc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 97302396d8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 16ec0ca1e6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new eb782202da 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 263494b859 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 5dc54a6b7d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new dddbae2d3b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 068b82f19b 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new f02c794054 349: onsuccess: #2169: 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 (64ec5ca78f) \ 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 1832 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31744 -> 31776 bytes 04-build_abe-stage1/console.log.xz | Bin 91572 -> 92480 bytes 06-build_abe-linux/console.log.xz | Bin 9432 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 236596 -> 236892 bytes 08-build_abe-stage2/console.log.xz | Bin 227652 -> 227680 bytes 09-build_abe-gdb/console.log.xz | Bin 38968 -> 39308 bytes 10-build_abe-qemu/console.log.xz | Bin 31776 -> 32016 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 2852 bytes 13-check_regression/console.log.xz | Bin 5628 -> 7240 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 | 29 +- 13-check_regression/results.compare2 | 61 +- 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/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 + sumfiles/g++.log.xz | Bin 2668688 -> 2664276 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 2275464 -> 2268144 bytes sumfiles/gcc.sum | 2292 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 894868 -> 896556 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214112 -> 214112 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436748 -> 439376 bytes sumfiles/libstdc++.sum | 12 +- 44 files changed, 1434 insertions(+), 1253 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