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 61a5aaa7706 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards 8cbb328f1bd 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards c29d5717f82 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 062ba409f2f 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 37ff4e0cba8 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 2c99ffcec38 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards ad29f658955 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 662204ddf77 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 580af7ca6eb 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards f1ca906c12c 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 6577d6b30c6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 8ca40c509dc 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 826e4766550 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 66537980aee 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 3cd2a393924 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 935f1fd6778 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 06edca517a3 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 159e21cc1e1 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 3cd0155cca8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards c4d7ae3a653 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards cba087c018f 194: onsuccess: #1995: 1: Success after linux: 517 commits discards a7a7b56e085 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 3860a571edf 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 45923efe69e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 68d11d1549c 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards de0e9f49f8f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 4d1360508ac 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards dd400f64ed0 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards fe6392ca364 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 9d1bb5a29c3 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards ad46bdc304e 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards d1a7ce9ee7b 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 4be979a94bc 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 99bc273b772 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 165c9d41664 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards e4170e4f2b9 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards b7c88f3129f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards cba001f39e2 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 986146c7e76 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards d43ceb3c573 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 44734a69aed 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 28e0c4dce04 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 991ed84f125 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 6341e44fa77 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 94c8c73505b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards f478651bc02 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards e956ba12d93 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 1bb063e0a1c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards ed71c9ff7ad 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 2ba7aa6411f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards e8380e9b69a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 8e3f8c35d12 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards cf8b05cae2c 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 02f9a6f95a6 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 9aac31d0a73 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 190c97cf66f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 184afe536d5 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 2dadd99c282 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 110c9634a27 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 905bb6f81e7 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 56bb5729f38 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 6e9c4442575 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 3ed9ddb9891 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards b6c490aa433 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 80a32360ebb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 2a064ea233a 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 9b0e3837a03 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 7df62492c96 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards e9d9dcca683 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 915fa632186 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 293ef4920dd 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 1d103a237af 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards b9e21310d2d 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 9a19024076d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 76294ae2e38 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 1ad3c4b1ab6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards a75a06c117f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 264ac9c4f19 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 56766dfc4ca 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 25472b82386 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c39f7071ae6 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards ce75bdec89c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 5b8b2133e64 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 5e062d28208 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards d13fb6759d7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 0c92132bf6c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards cb6c2d35b91 128: onsuccess: #1723: 1: Success after linux: 12 commits discards bf9e34412b2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards c00e807c67b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards fa3ae9bc3ce 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards bb1af43d95d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards bca6e6bec7f 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 513ae6d9851 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards cc3dfec7727 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 84c2d2b3069 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards fcbf730c961 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 196fc352de2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 96e8a7763f0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 43f8fa67c8b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 535f9b59945 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 5b84cb170bf 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c053a5a6014 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new db61b839f0a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new c8bde0883d7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 7cc3a9a3cbe 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 9071bdd0d53 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 8b0b3d6a20c 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new f9f1d49aaa4 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new fc6a82b50b1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 655cdcca6d6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 45e715ca51c 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 2098a64895b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new ca9c0ecc29c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 515d85571b9 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1db436fa48e 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 97bbe88faf3 128: onsuccess: #1723: 1: Success after linux: 12 commits new 28094074d36 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 8075aa3dd0a 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 251a7b5c774 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new a7ce1bfa1f3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 9a38d252b81 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 4152cee9761 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e0ddbbce553 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 28ccf769c5e 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 65857eff174 137: onsuccess: #1736: 1: Success after gcc: 5 commits new fb035758f51 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 33e61e27e02 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 43aabc8b4a6 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new ccce3667916 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new fc209df12ad 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new fb4bd0b6143 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 745612f37a9 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 3954a62ab16 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new c67d1c05f30 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new dc55f7eb870 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 1aab45351eb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 0d4ab94bea7 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 8f116b2184c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 3f3014c1ea8 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new f0a40214dc9 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new f94619cf696 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 06dc98eda52 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new ccb6226ccc1 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 6903de3f83b 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 8d23c2f0a38 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new f89c2b1bd01 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new b15de24eb04 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new c570703f793 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 639111ad41c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 44a3aeb94ce 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new dda75fae051 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new fedc8d94445 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 76948689250 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 2ae29785951 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new c1023b731e1 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 54eda0c71db 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 85300811dbe 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 2104895c0af 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 2115bafff1f 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 43bc3159ce9 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new e571a7b9575 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 3764dee5856 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 4af3ba631b0 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 2bbefb62f41 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new c10080f0fff 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 157b1066bd7 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 4816a035d11 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new ac215335028 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 77cf98786e6 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new ccdd251b144 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 89385dfd8dd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 5d534b28708 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 4db5318079d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 910d02ad34c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 3ad1a1b25ad 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new caf6a5860b3 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 4d1c25c3d9f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 504039d0b65 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new dc3847cb3c7 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 4ff1d9e3f3c 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 0a27f2e94e2 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 2023379ae6d 194: onsuccess: #1995: 1: Success after linux: 517 commits new 840c94fc29d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new f146342b4e8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 54b69755fbe 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 2d478177401 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 51378f669b0 199: onsuccess: #2000: 1: Success after gcc: 5 commits new f87096bfd47 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 3c0e40f3e04 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b4572ab35d4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 99a105db1c2 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 487299ac333 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new a0997f86494 205: onsuccess: #2006: 1: Success after gcc: 3 commits new a6fc206ab66 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2c55b2e81cf 207: onsuccess: #2010: 1: Success after gcc: 4 commits new ea18454faeb 208: onsuccess: #2012: 1: Success after linux: 12 commits new ed303a123a8 209: onsuccess: #2014: 1: Success after binutils: 12 commits new faf1605fddb 210: onsuccess: #2017: 1: Success after binutils: 6 commits new b2e9d002223 211: onsuccess: #2020: 1: Success after binutils: 10 commits new c4878aa0507 212: onsuccess: #2022: 1: Success after linux: 3 commits new c84591992fc 213: onsuccess: #2024: 1: Success after binutils: 3 commits new b868f073472 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new cbd1c2e5c9b 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...]
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 (61a5aaa7706) \ 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 1784 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32136 -> 31892 bytes 04-build_abe-stage1/console.log.xz | Bin 92436 -> 92596 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 238628 -> 236276 bytes 08-build_abe-stage2/console.log.xz | Bin 226232 -> 225540 bytes 09-build_abe-gdb/console.log.xz | Bin 38812 -> 38872 bytes 10-build_abe-qemu/console.log.xz | Bin 30612 -> 30772 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 3240 bytes 13-check_regression/console.log.xz | Bin 7860 -> 7248 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 297 ++-- 13-check_regression/results.regressions | 30 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 30 - sumfiles/g++.log.xz | Bin 2743108 -> 2710656 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2266628 -> 2319236 bytes sumfiles/gcc.sum | 2523 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 886464 -> 897364 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213252 -> 213128 bytes sumfiles/libgomp.sum | 29 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430640 -> 430068 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 1627 insertions(+), 1728 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