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 d52c3ede5a7 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 8d5779a42e8 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 26a11993af6 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 15867d41242 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 854fe802474 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards cb7344b9a87 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 6dc2e0bafb3 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 717ef64711e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards d7adb821b1d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards f3bcf0da951 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 9c2150a559b 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 64e335c8fd9 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards d75ee3c5bb4 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 355b38d2c36 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 799f40bfd7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards bb702e8c0b9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards 1535090b678 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 6d6023960b2 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 4baf6263b82 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards c4c5d479e36 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards adfc37f44c9 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards c26a9a61751 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 03a692f871b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 32b0ceff3ae 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 46090c03f37 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards da00d96554c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards babb1442a7b 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 2fa98174ad8 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 22b591226d8 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 5f6e6c06ead 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards daaa75a5da7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 44e10adb0f7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards c058b441428 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards daa9e7c162f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards ae812010e28 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards f7f8be68c89 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards e8a6855bb04 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 9013fccecb8 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 49c09eccb1e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 6da3bed79ef 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 5657c5911be 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 3c6c21aa45c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 57e42b03535 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 531d2468100 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards ea512f0cc7b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 85327b5ffce 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards d29cebf5f33 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 64b32c1d867 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards b35b558d680 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 48a44f6fc1e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 56d8ed2cc2c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards a6dc0616060 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 298c09f26c5 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 22d9bc6a308 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 426410f63bd 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards d14fa7d622d 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 3bc905a4a28 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 9ae043cb59d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 8a0edec3f1c 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards dc1fd430d12 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards a64ab32f70e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards b8b2c3cc150 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 01b3ce99c66 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards ec61d1cbe84 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards eb576bcb46e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 745d8edf2ed 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 5e455c17b3f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 5d4ffa813c5 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 1a3e01c9e3d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 4d254a531db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards b62e1c3b626 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 43d1b5fc12c 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 8233ed19288 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards cd05ee64113 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards ca325a5efbc 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards bbc2805ab2d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 212ecd18620 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 78a8e622131 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 65f085a4a0a 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards d24e91186f0 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 609e5fb52a0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards c6f24a96f14 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3e4639ddfea 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 5b9af7643a2 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 702afddef7c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards a1bbeba954d 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards f5e5a7e431c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 0378ac30d97 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 89cf72fbc7a 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 5682dbe9841 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 3dc7ceb5a5b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 23e29eb0623 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards e366e422118 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards 03d418f295f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 87b50ec8c6e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards e998989fdbb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 4792554ab75 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 26fb2dab8b9 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ffefe890994 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards 54e408f52d9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 20dab193578 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 370e82c21c3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new e257484f5fe 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 6a5675e8af1 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 5c4645eb529 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new bde1d9cadac 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 93aa3a17446 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 0ba15f9c4c0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new af35af6d411 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new 56813a168d1 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new d4c6bcc1243 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new fa8bb6dfcd4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new ef0d70689f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new df6154f3f28 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new b42a3529a86 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 0aa6e690a4e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new b03f93af2bf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 80363965cce 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new bd1b4ed92da 128: onsuccess: #1723: 1: Success after linux: 12 commits new 34d2a48e61d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 538c30f303b 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new db4ea052bfa 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 106b4a421e6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new fd4269c3154 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 678667a0170 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 8e825e6367d 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 830bb0b8656 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new a851c0d5d56 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 1bbaf895473 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 78d67571593 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 9dc072c7567 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 6c929b09ce1 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 71f7b4da119 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new fad72cbd845 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new cab760f6bf0 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 5138e64ef12 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 83279c225f2 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 99993f77443 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new fcbba4921e7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 6cd54830d27 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 8fb59b48b85 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new ebbf64821ef 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 5a72cb4cbd6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 05e8b6d7fe0 153: onsuccess: #1754: 1: Success after gcc: 2 commits new d38fb7e3faa 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 7125b7a4ad2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 7a1e2ce374f 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 348e24e4726 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 112cbe0c0f3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 4219cdcfd49 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new f6a934e2214 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new c4c5cef2d49 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 54f99ae3823 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new ad3fd8549ca 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 99de173533f 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 8257627461e 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 40459f70692 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new c7b2b8917d4 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 0fe09f1fca6 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 1bdd33f6438 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 6f8d2e23f55 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 712fd879fee 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 075bd39ecb7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 3f01197b176 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new f52e4dcc9dd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new 952ffb49c31 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new fdf138bb0ca 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 3f0aa0414e4 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 4e9bdf680ad 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new b9c5313d4ec 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new d837bb76acb 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new fbac3fd058e 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new f8236457821 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 23bc68479f0 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 53d9b440956 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 8b327978242 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 7fbe6bc05ad 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 87e04a1ff77 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 368ad50a5ff 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 1b7ec68d45d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 2e7dda6dca2 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 5c0d843568a 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 81766c7c50a 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new b6b37bc9bd9 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 331a40d7ad1 194: onsuccess: #1995: 1: Success after linux: 517 commits new 0083fdf6c5d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 8bca49aa67b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 6995bbbc5c8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new be722c82ad1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new c1c207781a4 199: onsuccess: #2000: 1: Success after gcc: 5 commits new b7f6930b6b4 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new cfc4889f7a8 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 5acc2192fa3 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 628939c85ae 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new a95a3307f2e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 5ed4587f356 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 55756871ae6 206: onsuccess: #2007: 1: Success after gcc: 2 commits new bdaacb27c49 207: onsuccess: #2010: 1: Success after gcc: 4 commits new abcd300fa3a 208: onsuccess: #2012: 1: Success after linux: 12 commits new b13f1b859f6 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 4c076ffd5d0 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 4199a67ece5 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 705027a25d3 212: onsuccess: #2022: 1: Success after linux: 3 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 (d52c3ede5a7) \ 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 1796 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31340 -> 31584 bytes 04-build_abe-stage1/console.log.xz | Bin 90800 -> 91152 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8772 bytes 07-build_abe-glibc/console.log.xz | Bin 236732 -> 238520 bytes 08-build_abe-stage2/console.log.xz | Bin 223420 -> 226796 bytes 09-build_abe-gdb/console.log.xz | Bin 39004 -> 39260 bytes 10-build_abe-qemu/console.log.xz | Bin 30596 -> 31216 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2456 -> 2468 bytes 13-check_regression/console.log.xz | Bin 5460 -> 4908 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 | 9 +- 13-check_regression/results.compare2 | 25 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/linux_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 2712844 -> 2712628 bytes sumfiles/g++.sum | 4 +- sumfiles/gcc.log.xz | Bin 2303160 -> 2305704 bytes sumfiles/gcc.sum | 2232 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894660 -> 891512 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213272 -> 213104 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432504 -> 436304 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 1246 insertions(+), 1327 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