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 08d1bcaeb16 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards abf8be904e5 212: onsuccess: #2022: 1: Success after linux: 3 commits discards bb3116eeff6 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards de93a56c606 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards bd0490200df 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 41485d27953 208: onsuccess: #2012: 1: Success after linux: 12 commits discards e858b1c32c4 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 2d4a1507bfe 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 898d0dea9be 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 083c6514b3a 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] discards afd2b9bb6c1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] discards 29ab552051b 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] discards 1b95a55b814 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards ae4cc1c7e9f 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] discards a4d02bcd817 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards b417d3c46c9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] discards 7d474f436f4 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] discards b7a71475eb8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] discards f380aebdbda 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] discards 2eb0249bcd9 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 01c10b32e43 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dd170886744 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] discards 0e6de209f71 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] discards c303c37b312 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] discards 5ca621569f5 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] discards 27a6e822d8b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] discards a436a788157 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] discards e2223774c79 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] discards e75e4e10f4c 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] discards c872b835726 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] discards 0ffd53fda50 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] discards 21c325e5137 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] discards 29b5089822d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] discards 05aae23d47e 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] discards 05217933436 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] discards 6265fb8bc44 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] discards f4146a8150b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] discards dca590f987a 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] discards 90790cc401d 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] discards ff6e45c651d 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] discards 03b31a5523b 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] discards 9679d0ad49a 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] discards 6f3f2ffca95 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] discards 323de939d95 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] discards 76066821b0e 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] discards a2aa5ebc370 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] discards 6b4fb514a7a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] discards 4c731dd0983 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] discards 73de395171b 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] discards 37df0f7b210 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] discards dc5f849d06a 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 6c62dba2d4d 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] discards 8f4fd4792e0 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] discards 8383c918cc6 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] discards d23b1df8573 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] discards 64b16b2dfcd 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] discards 8e55659970c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] discards fc759c56afd 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards f6773ee1395 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] discards 94ec4d3115f 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 649fcd802f8 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 6eb50e67abe 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] discards 8f5dec2f10e 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] discards 4cec6b48cbb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] discards eae6288f305 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] discards ac93173e88f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] discards 80c11907366 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] discards ece49fe7f94 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] discards fbc75855005 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] discards 3dc8f2e186f 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 30625542840 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] discards 4e10a672345 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] discards 369ff03144e 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] discards 121b2c8742a 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] discards e30c6c656d1 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] discards df2f36faf57 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] discards aeecab173a3 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 8c5692c455d 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] discards a2d90e676a0 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 90ae89d5b72 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 7a1496811a5 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] discards a02e63fbce7 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] discards c0c733bff8b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] discards 29ef8e75f59 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards af23b03c7e5 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] discards 9ef035f434f 128: onsuccess: #1723: 1: Success after linux: 12 commits discards d5cfc85afd8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] discards e33e2f5dd98 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 31f8777bf72 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] discards 3bb8cdffc72 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 65870ccb71d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] discards 22ec2d784f0 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] discards 77e14b6460b 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] discards 75f91099968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] discards 602c88719a6 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] discards f285520d6ad 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] discards e8626250af5 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] discards 807e3ba8ada 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] discards a8a68f301e8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] discards ffbbe376248 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 166693fb527 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new f2eee8e3393 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/ [...] new 5b84cb170bf 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 535f9b59945 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 1 [...] new 43f8fa67c8b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/ [...] new 96e8a7763f0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qe [...] new 196fc352de2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 [...] new fcbf730c961 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/ [...] new 84c2d2b3069 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/ [...] new cc3dfec7727 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/ [...] new 513ae6d9851 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/ [...] new bca6e6bec7f 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/ [...] new bb1af43d95d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new fa3ae9bc3ce 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 [...] new c00e807c67b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new bf9e34412b2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 [...] new cb6c2d35b91 128: onsuccess: #1723: 1: Success after linux: 12 commits new 0c92132bf6c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-2 [...] new d13fb6759d7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 5e062d28208 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/ [...] new 5b8b2133e64 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 1 [...] new ce75bdec89c 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 2 [...] new c39f7071ae6 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 25472b82386 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 56766dfc4ca 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/ [...] new 264ac9c4f19 137: onsuccess: #1736: 1: Success after gcc: 5 commits new a75a06c117f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/ [...] new 1ad3c4b1ab6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/ [...] new 76294ae2e38 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 [...] new 9a19024076d 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 [...] new b9e21310d2d 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/ [...] new 1d103a237af 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/ [...] new 293ef4920dd 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 915fa632186 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 3 [...] new e9d9dcca683 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/ [...] new 7df62492c96 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/ [...] new 9b0e3837a03 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/ [...] new 2a064ea233a 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 2 [...] new 80a32360ebb 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/ [...] new b6c490aa433 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint- [...] new 3ed9ddb9891 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb [...] new 6e9c4442575 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 56bb5729f38 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 905bb6f81e7 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/ [...] new 110c9634a27 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 2dadd99c282 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/ [...] new 184afe536d5 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/ [...] new 190c97cf66f 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 [...] new 9aac31d0a73 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 1 [...] new 02f9a6f95a6 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/ [...] new cf8b05cae2c 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/ [...] new 8e3f8c35d12 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new e8380e9b69a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 2 [...] new 2ba7aa6411f 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/ [...] new ed71c9ff7ad 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/ [...] new 1bb063e0a1c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/ [...] new e956ba12d93 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 1 [...] new f478651bc02 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qem [...] new 94c8c73505b 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/ [...] new 6341e44fa77 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 1 [...] new 991ed84f125 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/ [...] new 28e0c4dce04 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/ [...] new 44734a69aed 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/ [...] new d43ceb3c573 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/ [...] new 986146c7e76 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/ [...] new cba001f39e2 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/ [...] new b7c88f3129f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/ [...] new e4170e4f2b9 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/ [...] new 165c9d41664 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/ [...] new 99bc273b772 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/ [...] new 4be979a94bc 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/ [...] new d1a7ce9ee7b 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/ [...] new ad46bdc304e 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 1 [...] new 9d1bb5a29c3 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/ [...] new fe6392ca364 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 2 [...] new dd400f64ed0 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/ [...] new 4d1360508ac 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 [...] new de0e9f49f8f 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/ [...] new 68d11d1549c 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/ [...] new 45923efe69e 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/ [...] new 3860a571edf 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 [...] new a7a7b56e085 193: onsuccess: #1992: 1: Success after binutils: 151 commits new cba087c018f 194: onsuccess: #1995: 1: Success after linux: 517 commits new c4d7ae3a653 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/ [...] new 3cd0155cca8 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 1 [...] new 159e21cc1e1 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 4 [...] new 06edca517a3 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/ [...] new 935f1fd6778 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 3cd2a393924 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 1 [...] new 66537980aee 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 826e4766550 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/ [...] new 8ca40c509dc 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 [...] new 6577d6b30c6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/ [...] new f1ca906c12c 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 580af7ca6eb 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 662204ddf77 207: onsuccess: #2010: 1: Success after gcc: 4 commits new ad29f658955 208: onsuccess: #2012: 1: Success after linux: 12 commits new 2c99ffcec38 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 37ff4e0cba8 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 062ba409f2f 211: onsuccess: #2020: 1: Success after binutils: 10 commits new c29d5717f82 212: onsuccess: #2022: 1: Success after linux: 3 commits new 8cbb328f1bd 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 61a5aaa7706 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qe [...]
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 (08d1bcaeb16) \ 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 1788 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31812 -> 32136 bytes 04-build_abe-stage1/console.log.xz | Bin 91684 -> 92436 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 236872 -> 238628 bytes 08-build_abe-stage2/console.log.xz | Bin 225376 -> 226232 bytes 09-build_abe-gdb/console.log.xz | Bin 38880 -> 38812 bytes 10-build_abe-qemu/console.log.xz | Bin 30832 -> 30612 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2692 bytes 13-check_regression/console.log.xz | Bin 4920 -> 7860 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 10 + 13-check_regression/mail-body.txt | 30 + 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 187 ++- 13-check_regression/results.regressions | 30 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 41 +- results | 30 + sumfiles/g++.log.xz | Bin 2736348 -> 2743108 bytes sumfiles/g++.sum | 88 +- sumfiles/gcc.log.xz | Bin 2280328 -> 2266628 bytes sumfiles/gcc.sum | 2357 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891636 -> 886464 bytes sumfiles/gfortran.sum | 60 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213236 -> 213252 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429620 -> 430640 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1702 insertions(+), 1292 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