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 e9424b82f2 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 9aa44f5d69 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards ada52698e8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 3ff1f2e51a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards aa3456c6d4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards b74c5a7fc0 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards eb538f7ac0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 241e83161e 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 007bdd15f7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c93f4dc7b2 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 036da448dc 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 325b245ec5 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 2cb6c50aca 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards a5a5ec9465 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 4b8adabf28 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 6b54a6b87a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 647ae7e9db 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 8fd01c88bd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 825c484fb6 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 52ff27e1b5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b75fb9bc1f 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a924564aa6 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 951f3964bb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ca3670cdf8 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 3ff20669fa 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 6aba0cdbc2 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards aaea98cc7b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 8e39fe534b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 90d8c1b233 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 52d91fc5c7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 81c56b1e09 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8f267d3ea9 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards cc985fb26c 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 72a93e997c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards ab0afa5dbc 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 801ee11150 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 132701facb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards fb6effc426 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c1602d9ad2 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 221408bc41 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 1dce4b70fe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 1784b36f10 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 29b33bd57e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 365a693152 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards c5289edaa1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards e1cd40a28d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 5c99e9c130 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 755914604f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3a32913013 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 318c2b2d1b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards e5f585b676 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards be626d15d7 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6d9f3c858a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 202ef8e76a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 53603d6b4a 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 19e4f85514 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 49e14a0d00 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 3875232c13 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 0c9641b4fd 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 932786cf0e 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards dd72accb99 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards e0855443f7 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 08aed59823 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2ac55f9132 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards db870c6366 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 31d022f093 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards e49ec9aac2 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards bb0eab8f92 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1cb1f1fcc6 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 81d5c05e2d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 983aaa2f77 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0e96f6109c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0b3bb9cb94 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards aba6b1a915 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 75a3d6fc72 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards ceb3294532 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 88b0b4664c 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 50a05ef75e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards aac7773e63 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 5f4eef40db 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards f12bc97ac4 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 6b96b8493f 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards a66c0f00d1 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 0548eef401 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards da395ee036 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards c28f06f285 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 8d9bb98c77 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards f3498f8963 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 5bf8229aa3 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards c1094d1de3 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 4162c9de3f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 24fa0e96cc 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 3da36a5a3b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 5467601559 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 0224a151ff 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 7a77a030b1 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 66bc828c36 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 9c13ccbac1 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9a348aeaa3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards eabd94cb24 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 32f2c41bbe 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new a9d860c6a8 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 61c4c52e6a 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new bc4da5b62a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 08bc5cb93c 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new fa7f7fb258 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 56c7b693e4 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 83b68bada3 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d214f2b11b 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 46e9ba4c52 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new e0e940c1c9 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 92df4163e0 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 0fdad84755 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 29e8594f52 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 2355241d2a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 6f8c2d6b46 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new a9d22b4d53 287: onsuccess: #2103: 1: Success after gcc: 9 commits new ad3385337b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 1061749ac6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 6c08097492 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 6991905c91 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 16391a3ddb 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new cb13ad3463 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 22325f3541 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 527c6352f4 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 5aba65a595 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new d3f8996a45 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 63a143058c 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new db6b04f2a2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 0c63f4e0c3 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 11c355b96f 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5470bef6a6 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new d538d81af0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new ab97357dcb 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 011a61ec5f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 816eb509e5 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new b64704750b 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e9ce901fac 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 97a8316976 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 3aee5ec4df 310: onsuccess: #2129: 1: Success after binutils: 4 commits new ec084e7d73 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 817bb60bf8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new f765fd9ee8 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4c93c41bba 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 5731ccd756 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1cd93e84a7 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new a45c6ae5a8 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 18352d6f07 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new eb1d416617 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 8216ceb682 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e25ca5464d 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2435f2ccd8 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 7e811c348f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 44a4f183da 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 2352bd12f7 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4f56cc27c1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b9ca6484a0 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 478faf9666 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 92cc72b746 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 839c0b0617 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e23405b714 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 38e1ec4f14 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new fca29ac17f 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 7937a2119b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1d766ce57d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 6ed20445d8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f44b3143f5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 8eba3c7825 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2b4d776b21 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 4c9ae08d63 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new ae78ee4700 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 6bb202dd5a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 4d9cc71fa6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new ac07927e6c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new efe13fea0b 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 9031d14624 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 1f75fe704c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new bcb1d4cba3 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new efa91ec016 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 981be569c5 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new be51338283 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 0e47b016b7 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1275559f31 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 74d8f95cf4 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ddb2af922c 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 4106f5757c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new df3176fdc9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new ba95a0988b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 7be3f27207 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 8123ded034 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new adef036b97 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new b75c967022 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new cbb854a6b7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new be70549697 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 31952d46e7 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 61447184f7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new e928f92b42 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 88847e0af9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new ed4c9f8743 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 235050a35d 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 394bd3d40d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 9fd8b936db 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 56eedc7dad 373: onsuccess: #2193: 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 (e9424b82f2) \ 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 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31736 -> 36132 bytes 04-build_abe-stage1/console.log.xz | Bin 92660 -> 93156 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 238380 -> 237420 bytes 08-build_abe-stage2/console.log.xz | Bin 231564 -> 229972 bytes 09-build_abe-gdb/console.log.xz | Bin 39464 -> 43336 bytes 10-build_abe-qemu/console.log.xz | Bin 30800 -> 32500 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2952 -> 3188 bytes 13-check_regression/console.log.xz | Bin 8968 -> 7760 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 73 +- 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 404 +--- .../{mail-body.txt => results.regressions} | 74 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 40 + sumfiles/g++.log.xz | Bin 2651228 -> 2642652 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2225968 -> 2204756 bytes sumfiles/gcc.sum | 2158 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 894284 -> 904976 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214344 -> 214296 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435220 -> 436504 bytes sumfiles/libstdc++.sum | 46 +- 44 files changed, 1414 insertions(+), 1706 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (57%)