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 f67e315f61 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 87a139f239 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards f2eafc6162 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 33c7b5aa6c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 381c1291f6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 347e530c56 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards c9cb1f1c1a 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards 057f739c03 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 99e30bec03 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 2fc9efe792 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 29e41a862a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 0cfe68e88b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 57ea25f469 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards e47746ccf1 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 9c42fc1a9b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 00811a435d 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards ff0484fdbd 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards adeffc9bbe 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 4812dd51ad 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 01a5c229e0 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 5fe997ac41 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards c7684a5782 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 73da7ee904 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 8881e1998e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards ac0ca93f8f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 23ba8ebf54 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 83dbeaf609 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 75d8bb0243 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards bbf09fed91 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 72c1cc1a50 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 385dae9722 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards f2f7bd17bc 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards a4bd53d501 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 940baa97fb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards f22ad5525f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 11a6ac9057 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 96ef75f037 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 1b9255f57d 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards f4d071053a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 3b9e6613db 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 0802beeb49 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards bf4034db31 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 06a48a9848 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards c75d5f4986 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards daf5487172 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 688c443736 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 2a2afc3b95 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards abc91caa29 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 8a70c7813b 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 2787f756c9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards d4987b1dc2 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 66880a4261 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 464bd70178 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 9aaa621a47 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards fda6183593 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 72548ce875 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 63a8fb4a5e 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 6113bd20bc 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards eaf1bcead9 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 83820057b7 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e773c5ef3a 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 52c94f263c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards cf2aa68b93 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards f92b1997fa 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 04cbfc22fe 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1dc7d8a467 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3b25390c9a 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 713bc55b4d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 673655b6b8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards a00dc4431e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 52cebbc1d6 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 08e12cf109 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards d372021e7a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 2665bd040e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards dbe815ef03 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 0009a295d9 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 428029eeb1 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 573c80b771 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 88fe12dbfa 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 6b48cec774 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards dad3c12218 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 99da4b70e5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 55994884b5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards c19fb26787 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards d6bffacf7d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 08cb373c0d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards e564ead378 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 71be664758 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 9051e59697 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 5cfc0e3707 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards be5f8512c8 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 54cb43d058 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 6dd47f1520 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 9817ae1ffd 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 4df7d03bea 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 29455cbcfb 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d48c795616 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9d7e51e829 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 0ca28d3efe 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5d7ad9a045 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 829659ef8a 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 7a9b0cc3a6 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 0013e153b2 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fb0ce1526a 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ce2e67f33c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 0aa04df322 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 88bd02af17 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8be8a7ad3f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new af1f9cb915 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 63c3766005 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new b9faa934a1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 7b1e56ef6d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 74b21fa745 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new fdbe5415ac 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new bd07e93111 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 728fdd89d4 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 4fe48a2a6a 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new b990e799dd 104: onsuccess: #1697: 1: Success after gcc: 4 commits new da29a1d6ba 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a24daf8fe9 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 0f806a7810 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new b3654ef91c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new c8ed03d988 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 9e7fe8bc7b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new ce7528cab7 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new d45ae6ea09 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new b5f10bc7fe 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 1103cc1437 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 1620833ead 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new eef4d91f3e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 19b93612db 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 24978403fa 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 22593dde16 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 9853f8295e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 57c5f7ad03 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new a47f178ea5 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 36763c8668 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 381f0f0890 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 09d1c1bf19 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new efda5579b2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e22a89aaf3 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new c4e26b962b 128: onsuccess: #1723: 1: Success after linux: 12 commits new 8379786058 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 6d8be660d7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 8b0c6ec52f 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 50e419ead4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new a72140d22f 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 2c6e8f8ac3 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2a3a5c1a51 135: onsuccess: #1733: 1: Success after binutils: 5 commits new a1c183f3a6 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 3a942bf9ab 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 307d3d98b4 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 8cbb30e95b 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 9728192504 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new ee5c0dac3a 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 1613a8151a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 690d936289 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new e80fa5e83d 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 249885d73e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new e1eceee2f3 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 3b559d6ea3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new da86308821 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 5de8e4219d 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b6d7eb4cda 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 8911a00f78 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new e9bdee6c85 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 38cdd04a61 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 1cbf364fb1 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new c2cc606cbb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 476c76876f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 5c7b3f1b30 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 960ee3568c 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new e09a9154f3 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new feb2c25df0 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 07db1419af 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 47e1f83862 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 6e85a2c94e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 152586bb4f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 3db8560f7f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 733e33c15a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new c46d9417b5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new 78b4ff2f85 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 0334e98a76 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 276fc60b4d 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 8a7da7f0a1 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 627ae5fb76 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 08eb5668c1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 5b61677490 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 80468535e8 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 120d99278f 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new b071bdb7d5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 12d85b8d74 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new fcb7cc006f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 89361c54cc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new f2542ffccb 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new c4744a848d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new dbf1882418 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 09e73a662e 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new f430553ce7 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 9ce95c4e92 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new a6d1ff8836 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new fa81e832de 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new f617281985 189: onsuccess: #1912: 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 (f67e315f61) \ 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 1684 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30112 -> 30620 bytes 04-build_abe-stage1/console.log.xz | Bin 90304 -> 90144 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 236800 -> 235748 bytes 08-build_abe-stage2/console.log.xz | Bin 223168 -> 223504 bytes 09-build_abe-gdb/console.log.xz | Bin 37536 -> 37496 bytes 10-build_abe-qemu/console.log.xz | Bin 31112 -> 31156 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2708 bytes 13-check_regression/console.log.xz | Bin 5140 -> 7280 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 40 + 13-check_regression/results.compare | 47 +- 13-check_regression/results.compare2 | 87 +- 13-check_regression/results.regressions | 40 + 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 | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 40 + sumfiles/g++.log.xz | Bin 2679060 -> 2675768 bytes sumfiles/g++.sum | 130 +- sumfiles/gcc.log.xz | Bin 2249772 -> 2229680 bytes sumfiles/gcc.sum | 2670 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891804 -> 889032 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212888 -> 212936 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 435596 -> 429376 bytes sumfiles/libstdc++.sum | 32 +- 44 files changed, 1801 insertions(+), 1520 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