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-aarch64 in repository toolchain/ci/base-artifacts.

discards 1f7afb67f3 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4d8774fa85 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 2591ac7a9b 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 2104342eb8 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards c506410fa9 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 05d64ea5bf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 70e268c690 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 6eac475fe6 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards fa7606c082 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards dc67714697 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 220bbfa96f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards ad5b516905 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 28a5bdc30d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards f935ccc50a 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 7f242e2c11 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards d5d55f946c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards c4e3da3956 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 68b1a9798a 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 481221605b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 60107ff445 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 155889dd55 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a799cebbe9 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards fb6143b13e 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 4b82292c5d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 9b3e63538b 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards e48dc0c737 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards acb5b8ae99 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2cd85c60f8 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 733a78e715 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 33f2b9d88e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 49178c341c 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e1a35b1e96 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f4e9e36a0f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards ada1d33818 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 7bdebcd9b7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 33bdc20b85 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c80fb0f69a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 90a6ee30c2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards d52a26adde 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6711fb1ab8 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a2359ac45d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fdc4b6915b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 169ab687ac 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 4930e4b9ca 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1425c473e6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 7054f484cc 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards d6d19326dc 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1ab7f09e7f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 3ade4b4389 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9518cfd335 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards d7ce916451 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards f5a80ed131 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 99a5d856cf 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8cd676c6b2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 5d9cd90925 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards aa71205943 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards ff4334a77e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 20d9fcad59 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 021c0ade0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards aaeff03dc0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 27be44135c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 0e2c3a9afb 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 47faa46263 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 45ae2bcfe3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 372db16cdc 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards bb67332941 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ff8a993810 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1812a33fcf 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 49c59bb051 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 3f84fe5581 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b22ee34f35 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 68adcff119 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 461ec7ec4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 571cbe89a6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards af2e9c8189 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 797160124d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 70b4ce501e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1cd7c94584 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards f7d521dad0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8af1d2a75d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 66e2f26cfa 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 82502ce77f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c96db3ac93 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 729e8972cf 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 296a083542 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1963748462 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 66f889d8d6 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards afdbfed702 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 54b90716f6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards f993a7ea13 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 440f5d6a9d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards cac180946a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9cbea1feac 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards b9d234f5d2 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1974b37c48 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 82b3ef6b0c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c54713a387 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0f86a44d7e 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e7aad8cde0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 14ebae6124 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b7817d2281 75: onsuccess: 1: Successful build after linux: 44 commits new 4a3b97eb01 75: onsuccess: 1: Successful build after linux: 44 commits new 39b7336e9e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 420ad251c7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 128da2251c 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0599a70943 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9b4158a5e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1dfdae1ce0 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ab88fcf918 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new fcbefa43b7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 0bea8fa7ee 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 81935a3f1a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 50e4c51a96 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 7a6a6dbc94 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f1c3e6dd20 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 06bddf40bf 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 33d1fa1f9d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8eda5e8c96 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 90c4a82b22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3c8f3cf064 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ae5fcf5a24 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 5e82128882 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new beeb15d4f1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 21d10c223a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 84738e472a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 45db185a5b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new f88336034b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bdbd84caf6 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 00235d1f93 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new abe3035f55 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b2b2dfb136 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 6d656c802f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new bc5a9315c7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 4d50fd23ea 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 2e9f468705 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new a3833a4d97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f660066145 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7c254b46b8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new bca6124e86 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 819c712f27 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 61b94c2575 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new b0fa7bed55 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 642c75aac9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new a26f74d75d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 8a6e839b7f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6b7e318cfe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 62be23dfce 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new d30693f4d7 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6fe414c055 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 91f6c52c98 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8a3cd82e98 124: onsuccess: #2159: 1: Success after linux: 23 commits new c63957deb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8f2b0a770f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 184285697f 127: onsuccess: #2162: 1: Success after gcc: 9 commits new db1b0c9029 128: onsuccess: #2163: 1: Success after linux: 23 commits new fd531b9cfe 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new e805d7f386 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 3287920274 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 48da575c22 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new adc8b0725b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new db35c06119 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 0dc7ca4d91 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new c7baa4f85a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 12d30c91f8 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3c6dd08535 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6d85e978bb 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 81401379c5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7e2602bdc0 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 9d11439f1f 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 9a1d16493b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new b7258c87d4 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new fb05391b41 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cd3a596e0d 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 2197e4dabc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new cfbd2d0c55 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new ba22dd1df9 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 351544510e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 555bf676c6 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 6ebd35f1b3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new cf92d332d9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 924eb10eb4 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 8488f77197 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 3214c3fd58 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new d13758f6e7 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new e3818046f8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 655d588be9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 46708f3151 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new e9e07e49ca 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 194c84eadf 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 3f6ae22dc6 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new a73101c555 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ed5de251ed 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new fa0fb3ab77 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new d14da345a5 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e574fd7ef5 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new d98f35c58d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new ab83d54e18 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new a791fc71cc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new b2f32c5837 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b33a8eba9e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new cd30d35efb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new fd6319c799 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 19a1909b8b 176: onsuccess: #2211: 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 (1f7afb67f3) \ 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 1712 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31320 -> 30960 bytes 04-build_abe-stage1/console.log.xz | Bin 73284 -> 74712 bytes 06-build_abe-linux/console.log.xz | Bin 9048 -> 9204 bytes 07-build_abe-glibc/console.log.xz | Bin 240704 -> 240712 bytes 08-build_abe-stage2/console.log.xz | Bin 205472 -> 204396 bytes 09-build_abe-gdb/console.log.xz | Bin 38200 -> 37424 bytes 10-build_abe-qemu/console.log.xz | Bin 32048 -> 32052 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2940 -> 3668 bytes 13-check_regression/console.log.xz | Bin 7000 -> 6212 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 123 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 95 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 46 +- 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 | 125 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 3424824 -> 3428376 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3034024 -> 3030436 bytes sumfiles/gcc.sum | 4422 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037348 -> 1032772 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202248 -> 202468 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427756 -> 430016 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2398 insertions(+), 2690 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