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 bc610a8971 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 24b225adda 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards fc349e943c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 406b6e645f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards dbca80fb74 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 460b62a8d5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 068ab9312d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 9d1475df0c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards a703553571 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 529ed69d61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 0b7cd3550c 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards a7a13d8fc2 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 180d9311a9 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 443b4d544f 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 237a02a44d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 618a5610fe 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards bb3686f21c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 407438eb2e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 80391536fb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards abd7beedfe 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 43eae9c7d6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 33137acc62 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards f01f687c37 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 67e50d3151 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 536022d699 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards c26218715d 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards fc4415956e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 0a98fc5b5d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 10b301c4b3 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 124f741862 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 147e21802b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 239cd8791b 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards bc37d0aa93 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards f56f2a6b15 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 05e20aadb7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 48ef642f6d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards db0b499264 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 2143ee9c42 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 85e6f0cbca 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 838ffacb50 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 43f4383d9e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 05a1926501 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 8d86d79563 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d06c2fa18b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2fe98342eb 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d2145649c5 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 724b19e353 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ca302121e9 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards def66db8cc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 646f5c81d2 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards c516a906cc 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards b3b9517118 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 12804c0c77 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 69516c06f9 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards d9461a2976 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 5d34816400 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards cb0724bdcc 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 4b2edbd718 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 857a27bba8 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards e0e8710857 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 0bdb233794 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 2e0fea03a3 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards e07f932de6 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b4f421b97c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 566a0f33dc 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b7b383a730 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ea0f5c1ab3 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 98723018bc 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b02cb68e31 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 195ccdd0ea 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 3b28df09b9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 4960cddc0e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 24c4e205b8 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c3a50bc0fb 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards a427e145e2 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 90b96ea145 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards c290c114b2 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 81f79419ac 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards e9027e2b49 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f67238a3f3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e8f28b1ad8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 45c70be91f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards eebc0b217e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 5cf26b4633 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 9c3882334b 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 7d755e5416 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 31f26ac5d6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 2204c8e2b2 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 1f6665a073 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 8e9e801229 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards bab72d104c 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 5123171c40 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards b1a78ce0ac 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards a4e3dce242 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 6467b880a4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 6642aa1eed 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 0dfbc8fdfd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0b18b93a98 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 5b420d668a 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 8052cece19 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards d3ba6a3cc2 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new a797cf2531 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ab986f1855 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new b9799e5713 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 341a7b10b0 301: onsuccess: #2118: 1: Success after linux: 16 commits new 95819fe2e0 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 6e0993e979 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new f16f250004 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 538520e440 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 59101887fc 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 656546537f 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 57d70937b9 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 8031a0260a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new b3c9d371e4 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3c925468c7 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 6ef9a76270 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new c723de0550 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 8782e5d44a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 06a1f066a8 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new dbdd9066ed 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new c67814c943 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new e379d65857 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new afd5805ff3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 53c1f576e7 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e3e844a8c4 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new cdd0064c95 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new f4dccaec9d 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cf2b689f4e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 3f1406329d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4f182b987b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b18d271778 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new e0513fc8d8 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 54376ea16f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 7fd177386a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7da9ab6bf1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new f1b2c85fea 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 589940cfb9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6d16deb7c3 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 2741ca8d8b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d524d14283 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3ef4fb9e7e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new a7298c39da 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e3fcefd69d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new cb4081fe1f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 23a7b73d6f 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 434d12ce89 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new fae1848f77 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 578c5d2b34 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 95b7d31ab6 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new cdfce33717 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 6858b3c7c3 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7199c8d395 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new c022e9f6ce 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 5f8748a38c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 619246ef8a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new d724f3364a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new cc1b29e72f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 44a9a9b793 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 0962534b03 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 863c062534 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new f4691e5a90 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 5ddf92593e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new e4d15161e8 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new f18f17ae8f 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 104fec4ec7 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 74de8e8cda 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 828268708d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 9053e4f865 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 11907dd85f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new b069329300 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 3d048f52bc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 463f6cce4d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 8b595a982b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 6312ae19fe 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 63f30c86b7 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 47d21d63b7 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new fa51239410 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 24ff47e7c7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 200cc10f15 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new cf6e941483 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 4d1636bfd4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 4eba33ac65 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 5f5d3d3a5d 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 594c56e008 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new f972535fe1 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 121d174e60 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new a7ddc89b73 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1033dddcca 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 269fdd86c2 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 0318eb0903 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 3266fd9588 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 40beb573b6 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new f08fb32c5f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new c25c912a1a 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 153afa10a8 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b8d1657cd1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 2ef4cb4cc4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 9ccca4196c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 5455c66b0a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 1bf4fc9a1a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new cbf0a36724 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4dfb0f6f2a 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new f905526958 399: onsuccess: #2220: 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 (bc610a8971) \ 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 1820 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31620 -> 31116 bytes 04-build_abe-stage1/console.log.xz | Bin 92208 -> 92084 bytes 06-build_abe-linux/console.log.xz | Bin 9416 -> 9220 bytes 07-build_abe-glibc/console.log.xz | Bin 236904 -> 236868 bytes 08-build_abe-stage2/console.log.xz | Bin 228564 -> 229660 bytes 09-build_abe-gdb/console.log.xz | Bin 38612 -> 38328 bytes 10-build_abe-qemu/console.log.xz | Bin 31404 -> 31828 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2832 -> 2908 bytes 13-check_regression/console.log.xz | Bin 6536 -> 6484 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 13 +- 13-check_regression/results.compare2 | 35 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 44 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 40 - sumfiles/g++.log.xz | Bin 2640088 -> 2660544 bytes sumfiles/g++.sum | 15 +- sumfiles/gcc.log.xz | Bin 2195232 -> 2187636 bytes sumfiles/gcc.sum | 2380 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 891064 -> 888840 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216844 -> 216956 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437620 -> 435988 bytes sumfiles/libstdc++.sum | 35 +- 44 files changed, 1307 insertions(+), 1492 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