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 e9de057a43d 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 17def68b54f 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 7a3673524f2 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] discards 2df14d234a4 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] discards 98f87369448 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] discards a6c8538af5d 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] discards 87174822940 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] discards 45be50f4d8b 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] discards 65d29bbf306 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] discards 635140ca592 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] discards 856b836d6f1 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] discards 7cc91813e28 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 737c3a2ee42 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] discards 849d4681b61 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] discards 855c2c94c89 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 327589f9bdf 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] discards 63301faae53 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] discards 71dc7e24739 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] discards d3a40c47969 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] discards c5c47b1cd1f 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards a0a333d7476 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 5c452bac99b 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards d5dae83e032 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 5dd4545fc76 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 6dc1e2a15ec 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 073272dd018 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 68cb67d3a01 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards d08597a7c65 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 54d5e2c7fc5 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards 85486685f7e 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 11a9bbdac68 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards fe676f6aff3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 49234892ffb 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards dfdf7ce080d 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8bfeab54347 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 541c8cfbd2e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards 47373b6bc37 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards bce43513b0d 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 73adbd10096 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 4f19ae983dd 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards f692d707766 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards aaf8818cafa 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards 04ec169ef75 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 8123e617f8d 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards f6ecaa89782 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards dbd094242ce 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards cf178464fed 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards 8a3dc48fce5 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards 8fcb6866c62 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 09b580411a3 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards ac877667c07 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 2b7aeacf0cc 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 65cc6fb9ad8 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 0292e60dfb5 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 7f20a10ac45 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards d48109653fa 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards ec5e49834ab 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 26f0780e746 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards aa880173a98 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 1827309b40e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 604f98cc344 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards a5aef2539e6 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards ea0969d650a 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 8bb0c9feb5f 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards 1a861afe7db 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 1f5634eecc9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards bcf52b76611 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards e99371b0cd0 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards d56602f69c4 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards 9e50f53a0dc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 3b43cbb266a 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards bc00c8a223a 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 5edf14b761a 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards 4be89cf0c8d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 697f44d61bf 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 8bf8415c947 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards 32200643ef1 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 27bac6c7879 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 425c8025e0d 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards bded2320aa6 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 36997dde6a3 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 316d05efa59 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 31c4fb4f969 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards 97bbbac00f2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards 437767c45af 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 17a97b059e8 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards 53178a21bab 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards b924446f60e 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 82dc7954575 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 78c653331c1 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards f19830eda26 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 054d916db34 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 7968b159b3e 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards a38aa7d4138 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards f569da6cd60 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards f7ae7c9a751 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 2f58885fc0f 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards 5ddba33d7bd 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 76d9055fdc8 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 6d49028a069 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards 2b110f807f1 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new f6a4093415d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new 37838700b01 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new 2528dedf649 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e7591c4539e 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 5b3d4a836fe 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new e617b4dc8a3 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 19127a80d95 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 650384baa02 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 46e80cd0d14 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 19d0f873793 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new 0ca708ae574 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 371b058f5df 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new f2ef28859f9 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 42b270a64cc 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new 8841424a7b6 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 1fc4347929e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 8df310b5ea7 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 05e858ff6c2 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 1b708a38e96 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new 06000736387 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new c18248d44c6 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 8c9d22d08df 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 80e895d2b57 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 5b6b0c0b38d 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 6a08b0d1af4 156: onsuccess: #1757: 1: Success after gcc: 4 commits new efcaa3e58d5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new e57736c061f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 88d412923b8 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new ad8d6353cc6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new f11e0653447 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new ec40ce0f199 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 57acf1ecb02 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new cd8f72f3dc6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 0d45034ce0f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new fd9b4687874 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 932c1a92e0c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new e31a443fe4b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new 92130bcaccb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 558359c3a52 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 2c8949a1851 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new e29a436bd89 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new d4d399c3ac4 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new e793e777683 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new db0a796e2a2 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 1187235e143 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new 636ca7c37f2 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new fe735edcefd 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new f161bf55588 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 134e1ef8723 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 25dc5fa4e7d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new edb8d1d14c7 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new a21ff3818fb 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new 11177f017aa 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 8b5261ba870 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new ec248e05edd 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new 3d8a8ba7678 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new c440373384a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new e9e4a49c49e 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 4868e2efc5c 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new d8872d05b20 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 900eb06a991 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new b3ae3158a2f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 6dcf58dcc53 194: onsuccess: #1995: 1: Success after linux: 517 commits new 6412c94d042 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 73e2b9fd7f6 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 7a682ad0e2a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 42c1bcf0e2a 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 72ec1a3ac98 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 31c0047df38 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 7a87f91dd84 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 680e4cb7035 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 0daa4686882 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new ff1cb8cf1af 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new 963f3ffebde 205: onsuccess: #2006: 1: Success after gcc: 3 commits new b412a0b894b 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 9d66b05e00c 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 97a3910b8fe 208: onsuccess: #2012: 1: Success after linux: 12 commits new 4278f90ca78 209: onsuccess: #2014: 1: Success after binutils: 12 commits new c063ce430c1 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 9f938ce2376 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 49b6467ee08 212: onsuccess: #2022: 1: Success after linux: 3 commits new 5bad395c985 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 86d457bf751 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...] new f359baccd6f 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/ [...] new 2d3cdaefe0f 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/ [...] new 0cbd052828e 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/ [...] new 9672a3ad74a 218: onsuccess: #2030: 1: Success after gcc: 5 commits new d5ebc7acae4 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/ [...] new 72f302c662d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/ [...] new 2eded9e1f45 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 4df18b7942e 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/ [...] new 71617c30966 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/ [...] new 0a5296ec95b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/ [...] new a719945bf0f 225: onsuccess: #2039: 1: Success after binutils/linux/glib [...] new 3230c03e418 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 1 [...] new 1c3b9cfa75f 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/ [...] new 4c546b8f43b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-4 [...] new 9f06a338ca6 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/ [...] new 77a06c231bc 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/ [...] new 55f93e3ee75 231: onsuccess: #2047: 1: Success after gcc: 4 commits new eefaf339d06 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 0f6dbe2c21e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/ [...]
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 (e9de057a43d) \ 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 1780 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31536 -> 31584 bytes 04-build_abe-stage1/console.log.xz | Bin 91424 -> 91488 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 10260 bytes 07-build_abe-glibc/console.log.xz | Bin 234908 -> 235208 bytes 08-build_abe-stage2/console.log.xz | Bin 225112 -> 224904 bytes 09-build_abe-gdb/console.log.xz | Bin 38744 -> 38860 bytes 10-build_abe-qemu/console.log.xz | Bin 30404 -> 30188 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2840 bytes 13-check_regression/console.log.xz | Bin 5148 -> 6224 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 | 31 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 26 - sumfiles/g++.log.xz | Bin 2682708 -> 2682784 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2242348 -> 2232904 bytes sumfiles/gcc.sum | 2716 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893056 -> 892932 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213956 -> 214080 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427692 -> 427868 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 1592 insertions(+), 1646 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