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 f02c794054 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 068b82f19b 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards dddbae2d3b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 5dc54a6b7d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 263494b859 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards eb782202da 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 16ec0ca1e6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 97302396d8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards a399bafbcc 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards beb7695bb8 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 958164699a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 2858bd965e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 16969a97f4 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 38ef1d3e6a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 65cc509c9b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards d711b635ce 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 77e255b7fc 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 010ec78741 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 5802de9d81 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1d04c0c152 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 198ec8cb03 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards a7624463f3 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 757a39d751 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 201a916d7b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards ecf9ae513f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 17ea90fa49 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 28d1e1b740 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 8ed8492e33 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards c01bd30500 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards d9a5b8ff88 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 27ceb6ebc0 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards d0e12ceca5 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 4cf4cc614a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards a480010928 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 79bf05a17f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 039af5766d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 29bb795365 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 20c7d725cf 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 7ec6867af2 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c89d13b710 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 29d79d6542 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards afa1fe079b 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 35f43c7d01 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 3357eec990 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards db1bfe7515 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards c2e36059ec 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards ac89e41286 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards f5bdd5082b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 4f29d10bb1 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fd4dac2fe0 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards c4b84db67b 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 543a4ab697 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 0121d3f470 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c6409daf69 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards f98bea119a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards f291112883 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 78f9d5110b 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 6afe9e9642 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 39c28c5520 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 26a4e6ddd2 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 0a7d1e2be0 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 6f4f82e3e0 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 247db90f1d 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards fd38ab42fa 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 31e2c6e3c1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 5a0d805356 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 86bd3c8ebf 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards ab73119400 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 0c89211a40 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 1ce510a4f3 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards c7bd0ed8a1 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 32f9a92237 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards e306a6d8c7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards dbe98a8fa5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards d69951e35d 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 71a5a876ee 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 394367244e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 6a357a2e45 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 72a8c718b4 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 3ec8a7286b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 926aeb8723 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 01c2cd0fca 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards a6a27d887b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards e7fbd37961 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 30e56368fc 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 8df4e6ef22 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards d734b45ede 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards d94dd717ac 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 28e0226f61 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards be684a0fc9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 3862e3b6c6 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards f6102c0704 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 1dcb1e424b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards d19fc3bc55 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards c8712b1519 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 462820af19 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 8ed20a5e35 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards d627dd7344 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards d31abcfee0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 9dc99a4441 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 2fd9b260ac 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 8a9b1486f2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 4a395b4857 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 862df96257 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 721085db23 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cc0110c7a9 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 07866d81bf 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new f487357957 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new b9645ea1c0 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new b7270ccd99 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 314ce1155d 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 3af3765975 259: onsuccess: #2075: 1: Success after glibc: 2 commits new a12a704894 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 7a69a82639 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8882cb3f24 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 828009a026 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new f4121eb8bc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new f39777f4be 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new cec5e570f0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new f974fbbf59 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 6e57aae863 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new f987513783 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 96832c9d72 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 63ac8c24d7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 206c24c098 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 8979972978 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 8815ed32a3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new bc9b44ee3c 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new b40bdd77e5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 29c30ce701 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 374aed70f5 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 2b6979a5a6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new c5d21e4488 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new bb34d36ed2 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 945eeddaaf 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new ab718d3dbc 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 4a3dcb5bef 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 6467c4920a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 582f7cd61a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new e8f56ba207 287: onsuccess: #2103: 1: Success after gcc: 9 commits new c9f3caf337 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 6fecfb9e90 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 5c69583a44 290: onsuccess: #2106: 1: Success after gcc: 2 commits new c3a8e1b95b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new b94639cef5 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 03eddddf7c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new d6e5796ec5 294: onsuccess: #2110: 1: Success after gcc: 17 commits new c1f869b13b 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 2890ae8c46 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 6958fef786 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 18e9f7f6fb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 5a92c26c4a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 6e44a1a7f8 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 74e434acdd 301: onsuccess: #2118: 1: Success after linux: 16 commits new af78b771c5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 998e115cfb 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 9359e5a099 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 329fd4391b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 3a002ccaab 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new b970bdac14 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 3f10e287d2 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new e9ea8cca42 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 437d52685c 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 0cf1d99cdf 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 3d2db25622 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 5e55d3cfcb 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 78dec07495 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1b779e6f35 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new c0da2636f6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6ad3d6a748 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 5fb33db80a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 18503d0253 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 9b35e53d2f 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 53eddcecec 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 070240d720 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 7e7c5e9db2 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 317d1192da 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1dfffd2608 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new fe3a3ac73a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 9128c28d52 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new be875fd551 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 030b68fa33 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 91e4709155 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2d3ccc5fd2 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 8beb631c0b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 3677b304a8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e6b008b895 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b4a6c492b4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9530ee574e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 2cfafdbe3c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new fc3c953a7c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 4a00834482 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new c1da56b55f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new a7282ca1c0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 45aae30f98 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 0ce7f0e41c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 1253805c29 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 14b625a324 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0d9e7e85fc 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new c3cef7d8a4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b302d6829f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new d4cc92a24b 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 9100aaa008 350: onsuccess: #2170: 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 (f02c794054) \ 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 1740 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31776 -> 31388 bytes 04-build_abe-stage1/console.log.xz | Bin 92480 -> 92132 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 236892 -> 236664 bytes 08-build_abe-stage2/console.log.xz | Bin 227680 -> 229304 bytes 09-build_abe-gdb/console.log.xz | Bin 39308 -> 38904 bytes 10-build_abe-qemu/console.log.xz | Bin 32016 -> 31972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2852 -> 2940 bytes 13-check_regression/console.log.xz | Bin 7240 -> 7316 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 182 ++- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2664276 -> 2700616 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2268144 -> 2245964 bytes sumfiles/gcc.sum | 2151 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 896556 -> 900300 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214112 -> 214088 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439376 -> 444264 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1417 insertions(+), 1272 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions