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 fe7c6d45bd 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards de23f543a5 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards d7cb64f800 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 6b5c95e00f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 100478a8a6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 12d1e573b0 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 3eb2397652 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 936154bf96 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 9d1af8a991 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards b3a65d8a9e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 91c44b5723 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards d1546afdb9 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards f01f21258a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards 34806a0f27 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards a378ef1921 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 18d52ea155 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards c2b9517298 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards 567ecc3ad8 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards ebc993b6cf 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 102512eec4 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 213c6235d3 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 02603e4019 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 2ac481002b 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 1708ae9b31 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards fa204c4e87 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards fc07d3bb4b 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 2c50d16b90 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 76c70f4b63 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 1055baf283 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 5618c26f95 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards daea07c200 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 99da15cc31 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards bf29ca8837 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards a31be1066c 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards b1a18a8677 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 29f0b28473 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 4b0bd273c6 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 40f7e44e5d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards fb1b616b8a 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 04920cb7b1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards f602a02af6 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards fb627a3e37 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 306f69e941 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b93c9d81f2 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 311e2fd07c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 1da9d0cc23 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 4c5afab622 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 88e0da437a 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c61f53e993 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards b03dca0fab 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 754bb530fe 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards c07f066221 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 04b8f66958 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards a733d44600 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 877ad8f515 128: onsuccess: #1723: 1: Success after linux: 12 commits discards cef759c9a5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 7a8832d9c2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards bd58463b6e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 2fd5ce8199 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards f95d8e53c4 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 54ec9aeada 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 4acd4c0512 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 2981567c98 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 541f0bcec8 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 42126365cf 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 2c923f3c10 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 60f31406af 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards e1cf60d7e2 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 2f7ec5dc44 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3981e405bf 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 6b75269e24 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards d3e11bbfef 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards a06ad33106 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 75ac4a4d77 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 89d1ebebf5 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 9091061803 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 9ac4c686ae 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7df48fc9d2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards c3000a3385 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 88636d97f5 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 76958964df 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 45e1e01af2 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 45aaa5ab68 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards f8244cd400 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards c73b9c27d1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 8af9c376b5 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e0746d9d21 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3d4099767d 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 6bc3fc4257 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 99ddfdf19a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards da4e94e333 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards cb21440ee3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 57d6edc4a2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 81afeb6237 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 169ed2fa84 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 161e800fb5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 9eabfc4869 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards a036470a5c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 1c6178896c 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 07cc51a722 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 56aa6080c7 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new c4f332619f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 6dec740b56 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e463f67c40 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 369d9a36aa 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new df90d3d5fa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 7e24b95199 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 637421a803 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ab28d27f60 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 24974b4a3c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ba223ea38c 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new bebee7fb2a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 3b41afcbac 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 7988ef76bd 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 7998b9566c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new d7f2e5bc01 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f920c8c864 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 1861b0f757 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new cd37938e22 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 2bc8e0662e 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new cc5dc0097b 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b0e0d02424 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 05bbd70fdd 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 9a1bf2caa0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 95aab173eb 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 1a5dfccc52 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 7c9d1cfde7 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 48b05941d2 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d4e933d5b6 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fd2dfd280b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 93d3c60281 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new b6e9e6f449 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new f0f7b350ed 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f7f0488e11 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 04acb3d9f9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new b4be81e9ce 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new f514115359 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 5d7086e8ec 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new cfacef26c0 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new b6bbc85cf8 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7e934638e7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 1db4421c0f 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new af57c4d647 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 92266848e3 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new fd749a1c87 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 297c3e7dbc 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 16becabc7c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 7386b9cc34 128: onsuccess: #1723: 1: Success after linux: 12 commits new 6c1a78b072 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new e148dbe106 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 8ba9464b95 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new a24aee8014 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 34f4f43fd3 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 506d5e8308 134: onsuccess: #1730: 1: Success after binutils: 2 commits new ec76aa340a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new cad5fa92ff 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new e916478d1c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new e30569182e 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 329fd816f7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new c641063bd1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 7d0d3598f6 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new b49cbd5a23 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 04fcc78a47 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 0c0f8a51e7 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 0dd83fec66 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new f33452129c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 528c581f40 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 66300ce8f8 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new ff4cebac88 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new cf7cad01c3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 053a731492 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 26cd83a286 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 091ac2879d 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f23c8286bf 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new e02987729c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new b231a2dc61 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 807911f141 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 1a5f7d46fa 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 0eb51f67f9 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new 3b330c517d 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2c6c764fbc 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 42d78fde31 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new 2bdbe5bc40 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 56932c306e 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 170829a0a8 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new fa1825d43f 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new d0a3d82e4f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new fde3f2cd83 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new ef10100313 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new a2ea5e4fba 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 9f9f8f329c 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 6923aa66ac 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 7ae67bd551 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 5ab1eb4efe 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new 3c2bb93d74 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 7a0e848e09 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 1fe78b409f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 00b8dc1a11 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 10c0ec32ca 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new dee0a9c2fb 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new f05e628d94 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new c3fe9d0799 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 97ab9bce02 183: onsuccess: #1897: 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 (fe7c6d45bd) \ 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 1696 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30260 -> 30080 bytes 04-build_abe-stage1/console.log.xz | Bin 91524 -> 91020 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 233996 -> 235328 bytes 08-build_abe-stage2/console.log.xz | Bin 224676 -> 223236 bytes 09-build_abe-gdb/console.log.xz | Bin 37516 -> 37236 bytes 10-build_abe-qemu/console.log.xz | Bin 31360 -> 30920 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2816 bytes 13-check_regression/console.log.xz | Bin 6612 -> 13344 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 14 + 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 1209 ++++++++++++++- 13-check_regression/results.regressions | 52 + 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 52 + sumfiles/g++.log.xz | Bin 2699748 -> 2685100 bytes sumfiles/g++.sum | 407 ++++- sumfiles/gcc.log.xz | Bin 2223304 -> 2209384 bytes sumfiles/gcc.sum | 2473 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 885392 -> 891624 bytes sumfiles/gfortran.sum | 90 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 203456 -> 212980 bytes sumfiles/libgomp.sum | 543 ++++++- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423576 -> 432752 bytes sumfiles/libstdc++.sum | 33 +- 45 files changed, 3765 insertions(+), 1548 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