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 d5ee6079351 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 0f8177169ca 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 4710314b49a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 36a18eabbbb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 8925d35e7fb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards a11e3fa465a 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 601ae8b8e68 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards aefe76876a9 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 94b41893ff3 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards aca584e8cd9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 028706a9f53 194: onsuccess: #1995: 1: Success after linux: 517 commits discards e6266278aba 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 6549199210e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 3283bc82586 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 3411394b65d 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 9180933d312 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 8e4dd236f6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 286e2acec93 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards bb1d43114ea 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 0fc93c7daab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 5d291b385f9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards c21143c79cf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 006f4741437 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards b48e600079d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 14840d10696 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 49812204363 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards da224c2d9f7 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards 0bb82089f2f 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 6c8d7c407b0 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 5f250333fb0 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards 43d0fc1f800 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards c0ecc6916e0 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 49f75e5035d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 915030173c5 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 2e660dbf07e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards ab749d2c9f2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 732951a62a9 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards d5fefc2a98a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 15a0342147f 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 52174d11a3c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards a34c6ef6cca 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 64010928414 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 95dfabf6019 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards baa007db1c5 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards ff2f483a590 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 544108404a0 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards d26a9f728e0 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards d849b57fd97 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 00781161255 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 81c06cb3175 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 6df43c0609c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 3fd59454612 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 54d90205bc7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 4a77ae27c94 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 3fef091aa50 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 8930c26bd79 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards d3519a8fae0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 251b93d7294 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards bc0ff329bf4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards b781efa3451 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 39ea47b24ea 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 24b7650b403 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 3c111697a77 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards fb123cc2e1f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 3b7f82a508e 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards 45de75506a6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 554ef4826e9 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 1740955380d 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards f8350af317d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards a60701c1d6e 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 7d3db76d338 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards cd94950c266 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 383c2dd25b8 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 86129a36b4e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 6ac87e913dc 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 2d2c032a7d7 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards bf4ef2923a5 128: onsuccess: #1723: 1: Success after linux: 12 commits discards f4c06da0285 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 22b474441d7 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 06907812d85 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 032282a61bd 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards df360c70027 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 64664ceb655 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards f0c4e72f2cd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 46e17865c22 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 9481b8f8df5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards e597713fa0e 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards 34c6ed1de52 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 5e5201b17e5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 61ef0113af1 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards 69fb5e846ef 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 47c88926839 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards c27d63c6cb0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 27da207dac4 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards 83f7638bc32 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 842535b98d1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] discards 282e475aac0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] discards f8ff3de59e9 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] discards 2b3088e7d77 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] discards 4e4395e9d97 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] discards 47fd8c263e7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 532bc0109ec 104: onsuccess: #1697: 1: Success after gcc: 4 commits new a2938eda479 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38edde [...] new 3adc14c5af4 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/ [...] new 1da6e566b4a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/ [...] new d1e61369527 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 [...] new b54854011b4 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 [...] new 53bf5277fcd 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 39fc3530a0c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 9572a4ad71f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new 1472e198a41 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 4f2d7c610a2 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ad3752b2572 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new f258aaf9dcf 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new a1713e97623 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new a5fbf123d99 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new d215436795f 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 0bd2115b3b6 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 94adff5ebcd 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 0e21556e7f4 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 866041db85b 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new f09b988f96b 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 185e94b8354 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new 22831070a5a 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e850d19fbd0 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 392b73f410d 128: onsuccess: #1723: 1: Success after linux: 12 commits new b57afd2e65d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new 0556e6888c0 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new f1d8cbfed26 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 2c8c0859a9f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new fb0b6a2ee76 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new f48ce9ce1c8 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 3a8a16d5e67 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 30851602199 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 31f1ad2314c 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 28b612743ec 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new a43426d8808 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 4adcd620141 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 950aad31a21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new fadb489a2fc 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new bce59fd7791 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 82e4d1aa8d4 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 06a742dc2b5 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 61ea76cbcff 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 416fac0bdb4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new b33f245a5cb 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 4a50778a778 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new b7e49e94564 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 2f597d1c983 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 194e2feedc8 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 8237a25c5e2 153: onsuccess: #1754: 1: Success after gcc: 2 commits new daa945f696d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 59bb54d723c 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new b023ebc96d4 156: onsuccess: #1757: 1: Success after gcc: 4 commits new b796222fcd1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 0712f787544 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new b72b882c19f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 2a022636507 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 9541069843a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 66d65292d24 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 50386a15c4c 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new aecb5fb0318 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 65a9940cc93 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new f1e45e70cdf 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new a4294767c5a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 664692e4ae3 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new c15afe65490 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 0e6dd9a57d0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 822ab65e0c8 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new e933bb6a87f 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new f1a5770e2af 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 21bb7e8dcec 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new e223b346bfe 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 6c7b9804ebb 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 5addbc3620d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new 0762879ab21 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new 354f22044c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 954f542b87b 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 0fd9a527114 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 0539bb852e0 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new a42501e5351 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new e1845eeb010 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new e0fe0ecddf2 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new 442e16d9a7c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 77a23577199 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 598e173a5d7 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 956042c36de 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 91c21c745ca 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new c2696205774 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new f83460f38c7 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new d9c55935616 193: onsuccess: #1992: 1: Success after binutils: 151 commits new a62c722c5ac 194: onsuccess: #1995: 1: Success after linux: 517 commits new 0299d6177b1 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 0f38db5099c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 5f75ebc5721 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 25749b4d728 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new f5602088301 199: onsuccess: #2000: 1: Success after gcc: 5 commits new e92084862bf 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new a2e2744b8fa 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new e87d1bdb10f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 0cc2ee1baa5 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 4c495910780 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new a6199e3b0eb 205: onsuccess: #2006: 1: Success after gcc: 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 (d5ee6079351) \ 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 1740 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2812 bytes 03-build_abe-binutils/console.log.xz | Bin 31336 -> 32308 bytes 04-build_abe-stage1/console.log.xz | Bin 91304 -> 92468 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8724 bytes 07-build_abe-glibc/console.log.xz | Bin 235932 -> 237144 bytes 08-build_abe-stage2/console.log.xz | Bin 223788 -> 226908 bytes 09-build_abe-gdb/console.log.xz | Bin 38748 -> 39292 bytes 10-build_abe-qemu/console.log.xz | Bin 30368 -> 31496 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2696 bytes 13-check_regression/console.log.xz | Bin 5752 -> 6024 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 8 + 13-check_regression/mail-body.txt | 42 + 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 49 +- 13-check_regression/results.regressions | 42 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 42 + sumfiles/g++.log.xz | Bin 2714912 -> 2713740 bytes sumfiles/g++.sum | 14 +- sumfiles/gcc.log.xz | Bin 2305304 -> 2313092 bytes sumfiles/gcc.sum | 2594 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 895992 -> 898692 bytes sumfiles/gfortran.sum | 68 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213028 -> 213180 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425600 -> 440292 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1646 insertions(+), 1409 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