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 77777f5622 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards d0f631ae4e 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 7449cacdf7 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards e2aafec6d6 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 368b700956 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 0c6e91d83e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 3815a41068 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards d22c84847d 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 24bff27411 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 078c79bb8a 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 78a3728b96 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 52962a4ee3 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 489d8fdfd8 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards d55187f806 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 89e3e5b3b6 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 2f376fd5ed 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards c942fac2ee 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards e4074a8e8e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 5434494c6f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 970b64c1e1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 72770c0fa6 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards db4ec6f7aa 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards b9b5c5cfa1 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards e9110fcf43 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards fce679e79f 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 16ab57da86 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards b8fd950266 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards e815003cfb 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards e50aa02288 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 3bda7b10f7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 6fe1283e48 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 096c61fac5 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards d0062216d0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards f3dc0ac2b3 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards a7b0529d60 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards aef55033ff 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 856e9cabfe 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 2674fab028 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards b12006572b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards f69f66da44 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 85b7a4fde3 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards b75bde8c49 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 0dd284562f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 804667b8e9 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards a08f64f006 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards e1f39deb08 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 5fa344bcb5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards f32b692796 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 4ff35d9a5b 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards d235ac3918 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 4084bbcfdd 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 9077b65584 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards ba1e645aa3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 982c892d32 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 1d91240260 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards d241f7a417 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards e966135998 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 52dd87a67d 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 8db4a3e14f 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 9d4b9d1bb9 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards c27b46e635 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 92b282a3fd 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 6129421cb9 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 6f861eb43c 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 5507ea92bf 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 553ccf9259 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards b58e28a666 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards de777f1c42 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 76ec1007a8 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 6ae83beb74 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 33a82890a1 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 534b8e65e8 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards f20d0bf9b5 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards 5475ae31ec 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards 8f8b66a8c1 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 6da6085e01 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 595d4d36b3 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 4e17cefeda 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 96f47d15d0 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards b7d6168710 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 5cba1174d0 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 25b1bcaf3c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 5b65763aa9 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 511a60d413 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards d48311b3c1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards 6ee6196b4f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 078e08cd98 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards ad157fcc58 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 0754f30e80 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards 32b76d00e7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 1a501b4126 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 5dd390a19c 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 18b6c065df 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 46dc7af2a2 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 89030368c9 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards b4d16a6fac 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards ebd4773253 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 315bd74a5e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 43ea89c0d9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards d2e29553b5 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 61268492d3 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new ba2d30bbe7 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 427691c6f2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 55040d94df 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new 43fd253299 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new 38c6c30e1c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new a2ec043e0c 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 5d8b723409 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new c7e4c002c2 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 6d072d2e25 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 164a9cdc8d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 15a21e9780 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 4fdc14abe6 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new 2265174f7f 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 0487c0df91 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 96a12c7daf 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new f26e3368cd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 24c71512a6 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 41bfb145b8 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 1b827464e8 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 932182dbeb 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 2d086e9fa4 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 553ff09653 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 86c181b199 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new a0e29292b6 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 3f12dc50f1 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 050c5290bd 193: onsuccess: #1992: 1: Success after binutils: 151 commits new c17a3b561f 194: onsuccess: #1995: 1: Success after linux: 517 commits new 6c57cffeea 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new fe924ef179 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 0922299a2a 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 72a8b23d90 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 73ce96afe1 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 54e89d109c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 1871c50cea 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 5d8a74b746 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new ab86f3daa9 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 3539c52fbc 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new cf4ed5ceda 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 5ba3c7b8b3 206: onsuccess: #2007: 1: Success after gcc: 2 commits new b83ba6347a 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 0936d4e1fe 208: onsuccess: #2012: 1: Success after linux: 12 commits new 8ee57cd9e8 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 32bfc70ed6 210: onsuccess: #2017: 1: Success after binutils: 6 commits new ee652fe428 211: onsuccess: #2020: 1: Success after binutils: 10 commits new e5ebb755c7 212: onsuccess: #2022: 1: Success after linux: 3 commits new 9a19c0a66d 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 391e2750f3 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 312dabc727 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 77084952fc 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 0b3933dd78 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new a6cfbb27ba 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 0f052d3974 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 313aad8303 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 55aef8f4f0 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 38bc85fb2f 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new fd653420de 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 2b865c3f64 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 2f49910d54 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new bfc891c56d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new d753ac4512 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new efd60994f8 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 5c1574f4a1 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new abbdb4a4de 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 14ec47a05e 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 6583814be1 232: onsuccess: #2048: 1: Success after glibc: 2 commits new d3e8398909 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 0e2f035d06 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new e748fa2b89 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a0e6e41de2 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 84b6433f9f 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new daac7624d1 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new d84995b868 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 3f74c4e6f2 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 4fd96c9c64 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 98f40d3c38 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 3e16ca14ba 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 823d32bd40 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new a0b2763705 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 9703564c4e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 64a8e5b2f6 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 2e0da7d2f2 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 42aeb7edc4 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new d21a062b0b 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 95669a1e07 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new c2f9abaa6e 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 54fdd97a32 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 62705a360d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 05b95addac 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new eb40bcf333 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new aca782c82f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new e84f3c5453 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 0d1d2c3d18 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 382373384d 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new c0ac9dc1ab 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 708dab5f62 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new e66efd80e4 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 3d54ae34f9 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new d7eac62a08 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new d755a3e3e0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 72514f6b73 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 69e2c19cbf 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 480b1040a1 269: onsuccess: #2085: 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 (77777f5622) \ 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 1760 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32124 -> 32332 bytes 04-build_abe-stage1/console.log.xz | Bin 92096 -> 91708 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 9456 bytes 07-build_abe-glibc/console.log.xz | Bin 237000 -> 237280 bytes 08-build_abe-stage2/console.log.xz | Bin 225836 -> 224936 bytes 09-build_abe-gdb/console.log.xz | Bin 39108 -> 39184 bytes 10-build_abe-qemu/console.log.xz | Bin 31720 -> 31252 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2868 bytes 13-check_regression/console.log.xz | Bin 6848 -> 7332 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 27 + 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 64 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 27 + sumfiles/g++.log.xz | Bin 2650864 -> 2686620 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2271340 -> 2233164 bytes sumfiles/gcc.sum | 2609 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 891836 -> 894232 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214028 -> 214056 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 438420 -> 427724 bytes sumfiles/libstdc++.sum | 18 +- 46 files changed, 1642 insertions(+), 1519 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