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 e4b84e838c0 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 97f39a64613 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 48e2227ae70 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards afa6ef260d4 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 653e85c7b48 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards dd520e935c9 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards bf197f5d49c 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 9eaa828dc04 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 117e2e13a42 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 6a055428224 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards ad5baba04fe 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 28a788155ff 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 08561cb6887 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards ba2a2647cd7 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 7295cfda7af 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 187a87db95a 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 199ac86d751 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 6ddfbed886b 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 6b5651a849e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 836d5abf3e5 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 07dbb57416d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 407aaf9f483 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 07be56fdfdd 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 86f2cc211a2 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards fc9f3b38e69 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 8c26ad94bd0 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards ffc1661a5ed 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 8527f9472ef 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards dd79c8cbb5d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards cf255ceca07 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards c408c5cb8f7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards f24e6491e7a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards c693a15f0b4 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards d763f323f50 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 7605e384aa5 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 851538da36b 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards f933f8d90c3 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 66f4b9afd4a 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 6e01ba2909a 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 66de55595de 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 4b6ec57092b 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 4d3758491cf 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards fc9453317c5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards ffcb6df5838 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 0d2a85850f1 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards cdb56c44d8e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards fc6d30d3212 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards a99d89c027b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards a525f0d80b2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards bb3035e1711 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 0ff08f785e7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards bae9c362d0f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 2c2e6fd2b41 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards ffa7f460776 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards be2640b879f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 0e9a79dff65 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 38081c2bf32 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 3e9b8adee24 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 43c34ec0e21 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 5615fdc349d 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 75c282af6f3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 03c72808d4f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 95c045cf927 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards b8caf36ad1f 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards a44a47f5e1e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 1d9d4338281 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 9445df2374d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 072c92138d2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards bd38154ff22 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards ad6df4167cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards e7ee02c3437 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards c9ca9efe9c6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards a1a84ae51a8 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 8776b6e3b0d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 28de58989fe 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 129e0eb3c6b 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards c3ca703ff73 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards d7f37d2640a 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards e521308c5e0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 3e363ede102 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 2d1dffb05eb 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 7eaf72512a3 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e5cbfba51b8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 30d56dcfaec 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ae353d2b0e7 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 05d4b29cfe4 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 8bea826e23e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards f41c9aa0210 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards fbcd3fc8fcd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 6a33c299b98 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards e08821eabfa 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards ed7ac5b26a6 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 2d53340e8a2 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 39473b9486d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 2ac8a1dfee5 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards c6eaa8b2fd7 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards d8976088d35 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards b310cd7f94a 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards e0f8bb5f617 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards bdfd7f4654a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 3f0591fc4f4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 002f3c4dd1f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new d2c16e88eb1 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 835c259b242 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 9832664b2db 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 9418859e32f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new c229e1650d4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 346f8e93fb9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 9449115cc09 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new b147137d269 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new dd175b1ba34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 10c31a57b45 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new b10920fc84a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 3474ea1d595 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 761bbd0b4d7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 824a8bf3f81 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 46bcae44524 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new bffc062525a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 1d0ad5c51a8 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 579c0619bad 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 8d77da2add2 128: onsuccess: #1723: 1: Success after linux: 12 commits new 1d824a2891a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new a07df364693 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 77de02159bd 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 47ed58ab32f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 980fff721e7 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 3f89dcabf5f 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2b874c3c5b8 135: onsuccess: #1733: 1: Success after binutils: 5 commits new b888da9a4b3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 058e3c6b250 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 83535f02b4c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new cf12961c202 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new b2d90a678fe 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new b9e7635909c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new f6a06515a0d 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new cc88583a8de 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 82ac3be8f82 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 1be9ffab60f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 8651129c609 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 97b15aa543f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new e564a8b3e9b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new af718f7bc91 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new a5a9ccd4c0a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 4f81c073a5e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 0ff50a63c38 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new d3c00ed6c9e 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 5bbf8d7b7cb 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 0e5c7c5f3fb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 66b2665711b 156: onsuccess: #1757: 1: Success after gcc: 4 commits new f8c6fc11d66 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new fdb770f8d2c 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 874c919508e 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 28fdfa475ff 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new fa3f0f2adc2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 0c4d0c9fa7b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 2fc7dd2018f 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 51a53e016c6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 88beb1aba87 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new ea9d3e00f6d 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 0d7133ed4a4 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new cffd7cae4b4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new dc3d58d9f93 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 2491bfb6f4b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 04b3d770435 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 34027dd7d03 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 738e164be3b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new f46e1ad4998 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 19673abdbfb 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 0f775529dbc 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new c6ff0d793be 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 1425e848363 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new edbed2fc80e 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 9e528c362fc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 777219c7c28 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 57fc4993ebb 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new cf6ec9949fe 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 2201a9ce476 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 52d42e226dc 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 74c54b887db 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 00abd3cdad0 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 26e32db243d 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 301c289d163 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 2927eba48f1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 296dd201364 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new bd0b23059cb 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 81fe1a45a49 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 1b0e0ca4308 194: onsuccess: #1995: 1: Success after linux: 517 commits new b53e176efc8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new db1b20c085f 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new cbf099fe5fa 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 3527d643dad 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 2d1e8daa353 199: onsuccess: #2000: 1: Success after gcc: 5 commits new b152764c69f 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 4dbc30c9f9f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 6218bbf8a2b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 17e4a7250b7 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 6a9a0b49244 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new a1e9d7235a3 205: onsuccess: #2006: 1: Success after gcc: 3 commits new bb7c5f8e98b 206: onsuccess: #2007: 1: Success after gcc: 2 commits new faac667f541 207: onsuccess: #2010: 1: Success after gcc: 4 commits new b40550c45ad 208: onsuccess: #2012: 1: Success after linux: 12 commits new e6367727de6 209: onsuccess: #2014: 1: Success after binutils: 12 commits new a7e5f910569 210: onsuccess: #2017: 1: Success after binutils: 6 commits
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 (e4b84e838c0) \ 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 1924 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31756 -> 31528 bytes 04-build_abe-stage1/console.log.xz | Bin 91356 -> 91396 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8508 bytes 07-build_abe-glibc/console.log.xz | Bin 236876 -> 237332 bytes 08-build_abe-stage2/console.log.xz | Bin 223868 -> 224932 bytes 09-build_abe-gdb/console.log.xz | Bin 38976 -> 39040 bytes 10-build_abe-qemu/console.log.xz | Bin 30592 -> 30540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2416 -> 2484 bytes 13-check_regression/console.log.xz | Bin 5428 -> 5336 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 | 25 +- 13-check_regression/results.compare2 | 21 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 26 - sumfiles/g++.log.xz | Bin 2739924 -> 2735016 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2273992 -> 2294404 bytes sumfiles/gcc.sum | 2260 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893856 -> 892064 bytes sumfiles/gfortran.sum | 60 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213156 -> 213100 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430740 -> 427480 bytes sumfiles/libstdc++.sum | 6 +- 40 files changed, 1296 insertions(+), 1341 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