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 00a51b8d00 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 70dcbc4181 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b17c324163 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 47361d7cca 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e487a490f4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 754d97b73d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards ca2dbb19fe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards b320bbf42c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 37c4b6ca2b 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4419f6f849 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 8a0a0989d5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards ced2de7686 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d28424f691 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5b8977bc23 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 5e1999fa44 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 1e72a28235 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 8952f7473d 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards d629423b4e 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 715463d37a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9721e90cd7 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 26d65230ce 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 1808135c47 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards c4b798bb27 301: onsuccess: #2118: 1: Success after linux: 16 commits discards fb7abceb4b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 126e212d80 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 0e6d7d20dc 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 12c414bbb7 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 8f285816f5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 1141fbe40e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards fffc28258d 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards edbfa3748a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 96edf213e4 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 9b5838f092 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 1476dd54f3 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards c3af85fb59 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards e1916590f5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2177a6bd36 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 82d09c7bcb 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 1b17bdba4e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 20224215b5 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards ceecaa8d1c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards af1183ef7c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 4ecdead448 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 742b5c7295 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 90a179602e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards e336c5ad48 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards b400ac84c2 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 839820672c 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 8891b6ff71 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 9be700a3a8 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 9844c95a03 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 7e3d2f9d53 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 82137033a3 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards a8f752fa62 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards f0aa7b2cc0 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards fa62c0f4f2 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 2502bcc75d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 724905fe13 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 8aeccea50c 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards c423c4ff20 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards e1a0ce34c6 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards b96f4512c3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 2fec75e37a 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 447ce5d4d7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 542fed25cf 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 9c8dcfe1cf 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards e8fe47639e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards a43a278148 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards e53858b8b0 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 1544e1da49 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 36f3f7b87a 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 790e305839 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 0b5bc76e38 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 29bbd8e8ef 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards a22a2cf2f4 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 460bbe6d3a 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards f8dc255834 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ce46e07027 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 11ced676ec 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards aa7ab63d9b 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 95a3d8b394 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 10713a5167 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards bda719edf6 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards e04a1afecf 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards f49f7e9391 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 0a311f38c6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 06e8e4f34a 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards c6346a3ac0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards f9d4503e3d 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ed57bb2520 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 655aeb29b2 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 571ed43036 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 71dd5b6b12 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e269f52bf4 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards fe9a7eb6ea 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 829bf14865 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 876ce54680 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 30433c734d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 4a04510654 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards e40c8dd8b9 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 61871bc5f7 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new f6f096b580 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 4eb2af3ce6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new b349b27bd4 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new b04c3a1df5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new e02cbd6c09 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new d7594809d8 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 99802c01bb 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 8d7f7ea1f9 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 42dbbef729 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 0574b23084 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 5f5ffadcbe 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 1081d99553 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new a3d1b85f2b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 48548f5836 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 4b748f8077 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 8ad9fba2c9 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 4062cc01eb 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new ee90188f3f 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 2ee4374c59 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new c087aeefc3 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 94d8456d0b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 2e5c7302b0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 1a3592b907 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new c7b963bcd5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 306a53bdb4 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 8e35d00893 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 67cd8f4609 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 44df481373 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new b873fa2aae 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 2ca3e758ef 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cd974f2eff 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 923d7437fa 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new ec2b63328f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 6e7f68e689 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 17ded5157d 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 2d4fb81781 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 1d734792a0 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 555f6ede3d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 5d68099e8d 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fd9cb81f4f 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 2c18ce1f3b 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 953ac5f22c 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 92d7b16d5a 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new aad6f32e99 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 292d732862 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 125e5e961f 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 3d1a7c77a2 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 54b51e093b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 84bc4c5236 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new c03d29ceed 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 9260376c31 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 480dab3b3d 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 4efbfa1d43 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 32438e04ad 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 37cdb08372 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 5b0c482094 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 1dc5880450 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 55e19da595 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 2148a0511d 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 5ce170de56 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 9c37b79e45 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new bc6971c5c1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 14380720fc 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new bbce63d26d 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new cf03ad0ace 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 8a8476e974 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 04525c6d19 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 513b2957f4 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 14e7bbb2b2 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 6126318c58 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 6f30395e34 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new aa47f4a3de 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 45ce1f8242 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b44c2c5914 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 2afbe6ac78 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 20e7fd44cb 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 9c445ec57f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new afefeb7751 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 2317324f13 301: onsuccess: #2118: 1: Success after linux: 16 commits new d1434b95df 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 78b686f224 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new d0d6fca2a9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 9b710c46d5 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 71bdefcf31 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 109c7123e2 307: onsuccess: #2124: 1: Success after gcc: 2 commits new c583d87f34 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 34811d0443 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 66615c7b2f 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3af2d9a3e1 311: onsuccess: #2130: 1: Success after gcc: 4 commits new a9c41e2d03 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 750ba9224a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 259cde4883 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1fec3ad8a6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 8af726ea3c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 47d3180444 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 2798eead8e 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ec6cf8501d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e1ffc1cc02 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 6047fe6270 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 7a8faaeb07 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 35a2d1b231 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8d27b5631a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...]

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 (00a51b8d00) \ 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 -> 1840 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31760 -> 32680 bytes 04-build_abe-stage1/console.log.xz | Bin 91592 -> 92396 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 236260 -> 237516 bytes 08-build_abe-stage2/console.log.xz | Bin 227792 -> 228240 bytes 09-build_abe-gdb/console.log.xz | Bin 39320 -> 39516 bytes 10-build_abe-qemu/console.log.xz | Bin 31132 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2652 bytes 13-check_regression/console.log.xz | Bin 5296 -> 7452 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 13 + 13-check_regression/mail-body.txt | 63 +- 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 83 +- .../{mail-body.txt => results.regressions} | 64 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 65 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 47 + sumfiles/g++.log.xz | Bin 2689948 -> 2660992 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2245012 -> 2282024 bytes sumfiles/gcc.sum | 2399 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 905160 -> 898024 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214156 -> 214264 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434412 -> 446152 bytes sumfiles/libstdc++.sum | 54 +- 43 files changed, 1603 insertions(+), 1386 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} (60%)