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 a7e5f910569 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards e6367727de6 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards b40550c45ad 208: onsuccess: #2012: 1: Success after linux: 12 commits discards faac667f541 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards bb7c5f8e98b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards a1e9d7235a3 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 6a9a0b49244 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 17e4a7250b7 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 6218bbf8a2b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 4dbc30c9f9f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards b152764c69f 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards 2d1e8daa353 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 3527d643dad 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards cbf099fe5fa 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards db1b20c085f 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards b53e176efc8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 1b0e0ca4308 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 81fe1a45a49 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards bd0b23059cb 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 296dd201364 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 2927eba48f1 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 301c289d163 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 26e32db243d 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards 00abd3cdad0 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards 74c54b887db 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 52d42e226dc 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 2201a9ce476 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards cf6ec9949fe 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 57fc4993ebb 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 777219c7c28 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 9e528c362fc 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards edbed2fc80e 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 1425e848363 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards c6ff0d793be 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards 0f775529dbc 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 19673abdbfb 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards f46e1ad4998 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 738e164be3b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 34027dd7d03 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 04b3d770435 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 2491bfb6f4b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards dc3d58d9f93 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards cffd7cae4b4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 0d7133ed4a4 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards ea9d3e00f6d 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 88beb1aba87 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 51a53e016c6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 2fc7dd2018f 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 0c4d0c9fa7b 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards fa3f0f2adc2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 28fdfa475ff 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 874c919508e 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards fdb770f8d2c 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards f8c6fc11d66 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 66b2665711b 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 0e5c7c5f3fb 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 5bbf8d7b7cb 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards d3c00ed6c9e 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 0ff50a63c38 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 4f81c073a5e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards a5a9ccd4c0a 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards af718f7bc91 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards e564a8b3e9b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 97b15aa543f 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 8651129c609 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards 1be9ffab60f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 82ac3be8f82 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards cc88583a8de 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards f6a06515a0d 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards b9e7635909c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards b2d90a678fe 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards cf12961c202 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards 83535f02b4c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards 058e3c6b250 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards b888da9a4b3 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 2b874c3c5b8 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 3f89dcabf5f 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 980fff721e7 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 47ed58ab32f 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards 77de02159bd 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards a07df364693 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 1d824a2891a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 8d77da2add2 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 579c0619bad 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards 1d0ad5c51a8 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards bffc062525a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 46bcae44524 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 824a8bf3f81 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 761bbd0b4d7 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 3474ea1d595 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards b10920fc84a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 10c31a57b45 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards dd175b1ba34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards b147137d269 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 9449115cc09 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards 346f8e93fb9 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards c229e1650d4 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 9418859e32f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] discards 9832664b2db 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] discards 835c259b242 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] discards d2c16e88eb1 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3c523fe3c7a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 20dab193578 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/ [...] new 54e408f52d9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/ [...] new ffefe890994 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 26fb2dab8b9 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 4792554ab75 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new e998989fdbb 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 87b50ec8c6e 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 03d418f295f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new e366e422118 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 23e29eb0623 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new 3dc7ceb5a5b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 5682dbe9841 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new 89cf72fbc7a 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new 0378ac30d97 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new f5e5a7e431c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new a1bbeba954d 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 702afddef7c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new 5b9af7643a2 128: onsuccess: #1723: 1: Success after linux: 12 commits new 3e4639ddfea 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new c6f24a96f14 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 609e5fb52a0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new d24e91186f0 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 65f085a4a0a 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 78a8e622131 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 212ecd18620 135: onsuccess: #1733: 1: Success after binutils: 5 commits new bbc2805ab2d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new ca325a5efbc 137: onsuccess: #1736: 1: Success after gcc: 5 commits new cd05ee64113 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 8233ed19288 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 43d1b5fc12c 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new b62e1c3b626 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 4d254a531db 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 1a3e01c9e3d 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 5d4ffa813c5 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 5e455c17b3f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 745d8edf2ed 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new eb576bcb46e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new ec61d1cbe84 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 01b3ce99c66 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new b8b2c3cc150 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new a64ab32f70e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new dc1fd430d12 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 8a0edec3f1c 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 9ae043cb59d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3bc905a4a28 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new d14fa7d622d 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 426410f63bd 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 22d9bc6a308 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 298c09f26c5 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new a6dc0616060 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 56d8ed2cc2c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new 48a44f6fc1e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new b35b558d680 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 64b32c1d867 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new d29cebf5f33 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new 85327b5ffce 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new ea512f0cc7b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new 531d2468100 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 57e42b03535 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 3c6c21aa45c 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 5657c5911be 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 6da3bed79ef 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 49c09eccb1e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 9013fccecb8 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new e8a6855bb04 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new f7f8be68c89 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new ae812010e28 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new daa9e7c162f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new c058b441428 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 44e10adb0f7 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new daaa75a5da7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 5f6e6c06ead 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new 22b591226d8 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 2fa98174ad8 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new babb1442a7b 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new da00d96554c 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 46090c03f37 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 32b0ceff3ae 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new 03a692f871b 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new c26a9a61751 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new adfc37f44c9 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new c4c5d479e36 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new 4baf6263b82 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 6d6023960b2 194: onsuccess: #1995: 1: Success after linux: 517 commits new 1535090b678 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new bb702e8c0b9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 799f40bfd7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 355b38d2c36 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new d75ee3c5bb4 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 64e335c8fd9 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 9c2150a559b 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new f3bcf0da951 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new d7adb821b1d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 717ef64711e 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 6dc2e0bafb3 205: onsuccess: #2006: 1: Success after gcc: 3 commits new cb7344b9a87 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 854fe802474 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 15867d41242 208: onsuccess: #2012: 1: Success after linux: 12 commits new 26a11993af6 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 8d5779a42e8 210: onsuccess: #2017: 1: Success after binutils: 6 commits new d52c3ede5a7 211: onsuccess: #2020: 1: Success after binutils: 10 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 (a7e5f910569) \ 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 1792 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31528 -> 31340 bytes 04-build_abe-stage1/console.log.xz | Bin 91396 -> 90800 bytes 06-build_abe-linux/console.log.xz | Bin 8508 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 237332 -> 236732 bytes 08-build_abe-stage2/console.log.xz | Bin 224932 -> 223420 bytes 09-build_abe-gdb/console.log.xz | Bin 39040 -> 39004 bytes 10-build_abe-qemu/console.log.xz | Bin 30540 -> 30596 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2456 bytes 13-check_regression/console.log.xz | Bin 5336 -> 5460 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 | 8 +- .../results.regressions | 43 - 14-update_baseline/console.log | 70 +- 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 2735016 -> 2712844 bytes sumfiles/g++.sum | 28 +- sumfiles/gcc.log.xz | Bin 2294404 -> 2303160 bytes sumfiles/gcc.sum | 2068 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 892064 -> 894660 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213100 -> 213272 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427480 -> 432504 bytes sumfiles/libstdc++.sum | 6 +- 40 files changed, 1219 insertions(+), 1236 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (73%)