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 26906d9048 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards e92516a580 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 7ab5907257 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a28db6f5e4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b08605598f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards aab2f0fa4d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c16129e305 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 759ae3a30a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 99d83fba01 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fb508161f8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 1d1655d11e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards a26ad4fd07 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 8af3e80cf5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards eb2c859e54 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 8a910efdaa 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 505c3a68a6 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0e3b5d32ab 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards d3a40d924a 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 27f2258719 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7187e18786 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 884bebd4ba 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e965718bd8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 32809d4eb0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards a27bcc5607 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards fc09516b32 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 5291dcb8b6 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 574e643219 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards e82449c06e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 1d12e38e3a 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 1794ca6a06 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards d9aded48cd 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards e0c4979690 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 26838f1feb 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards a9c8529374 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 313059d4eb 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 447226fef7 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards cde93bbeca 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards b559547472 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 4030888c70 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 98f1f417a1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 3709d4d381 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8cdb896001 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 7bd665a5ba 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 1c00da0f8a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards dbed0ac7e8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 062bee2dcb 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards cbd87e181c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 4a1f9bd93f 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards e9d981e501 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards c475910e2f 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 1ab474f2c9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards e95b6b74cb 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 9e9601db00 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards b708ff5329 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards d86d1a26c2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 059015e216 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 487aa56654 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 2e8ce3a743 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 75097f0856 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 014c407752 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 3f8bc17dc4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 08b668ecd4 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 7571d41bde 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 48b6ab0ac0 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 56f33dd94b 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1914fd28cc 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards e35b6427af 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 142f60deb0 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 65eae2a006 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards f3492ac6f7 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 00058f56a4 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 21063cb952 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards b83857a9b2 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards ae67119433 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 876b6b5c84 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards e36bcc6fdc 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards b90115ed27 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 2b8f20971e 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 8d46811724 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 08e1971dd6 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards b22dfb25b7 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 1cf2880338 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 1689779a9b 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 2880342d8b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards c9c6c1dd99 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards e967bde8c7 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 49faa48700 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 0c8210bcb7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 0c0d9aed54 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards c676bde5aa 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 509ff5d40e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards a8addfbad6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 1ad5142c1b 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards e2c8b9557e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 6d24c2a1d9 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards ec8676d2f2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards b8f80e0fc6 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards a7d5a7d68f 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 89c6cd8de5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 3f935a9a99 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 7b850707e5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new feb399249e 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new ebdfa705f2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 8cb76f21c4 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new cd351f9ac7 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new c1e888530a 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 4e04f265ba 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 0d337a688f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 77d941a6ec 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 06a64bb3f7 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 6c7e863c66 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 8a575110c2 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 3974b3401b 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 4e6d63fdd0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 2e612b2d6d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d3329a7d8c 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new e2cccc10d1 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 7090d821b1 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new c1d58afe4c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 17c358874f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 8e05f8130f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new be6b88230f 259: onsuccess: #2075: 1: Success after glibc: 2 commits new ae1a7b60fe 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 03afaf08c9 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 96819ec8ae 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 391e94d39f 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 3d25d337de 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 8a606c2d87 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 980364d4fb 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 5fe5a2c663 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 9baec8b58e 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new d3dfad1485 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new dd2f84dcd5 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 92f8a4b0d0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new be4c56006a 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new adcfb42fb4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 77a25a97a4 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 0805d4500a 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new e5034cccbc 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 974b6331e6 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 53e80db0c2 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new c54ba770de 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new f5645166db 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new b144a5339f 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new a07817aaf3 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e3b8afd69f 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 2f3a66611e 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 92af2fb105 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new fe683f144b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 60ffa70fbc 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 6e191ef572 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 320aa77326 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 1bf9b26163 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 30d39c2452 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 095ef7edda 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 71405c0085 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new aca4c41adf 294: onsuccess: #2110: 1: Success after gcc: 17 commits new e6d377f160 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new b2d1543a87 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 37a3377b5c 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new f08d03b669 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new a90c80ab3f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 2f7b95e4dc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 93c969ac91 301: onsuccess: #2118: 1: Success after linux: 16 commits new 1b8ec06a6f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 626d2675ee 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1a2a811525 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 666b2a8213 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new ccabc5b122 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new b00fd43e99 307: onsuccess: #2124: 1: Success after gcc: 2 commits new ed290f1845 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 7dda451f82 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 047f97e0da 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 121cdbd9c3 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 503494f2e3 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 1ac0556465 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 1084c8f45d 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6d1fe995af 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new fa5c8b94a5 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 68be55e2ea 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new d1d5cf3c3c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 853cb2976f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 96f810bd56 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new a1c8ee0891 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b6e4d11dde 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 80e6adbdf7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new dd3f732de4 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 7da0e48e1c 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e753820f47 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 5236f5dcbb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 980662f8ca 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 9dcb09b345 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 74d06a9c7a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2dfc3f9a07 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ffff3b0cbc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new e93ee41472 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 67632a82ea 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new bf0577c2be 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 68023ec231 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new eeca83781a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 0a17151a77 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 95c4cb1966 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d9c2e15c86 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...]
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 (26906d9048) \ 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 1780 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32420 -> 31824 bytes 04-build_abe-stage1/console.log.xz | Bin 92636 -> 91720 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 238272 -> 236000 bytes 08-build_abe-stage2/console.log.xz | Bin 231304 -> 228824 bytes 09-build_abe-gdb/console.log.xz | Bin 39692 -> 39272 bytes 10-build_abe-qemu/console.log.xz | Bin 31504 -> 31136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2812 bytes 13-check_regression/console.log.xz | Bin 5592 -> 6360 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 | 31 +- 13-check_regression/results.compare2 | 52 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 + sumfiles/g++.log.xz | Bin 2662812 -> 2692248 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2271064 -> 2246972 bytes sumfiles/gcc.sum | 2175 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 895108 -> 897412 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214136 -> 214240 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429432 -> 441816 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 1338 insertions(+), 1199 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