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 aff339e825 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards ad37064fd2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards d3301d7980 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b417f833ba 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 0ba59f2241 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards d66d7ddfcb 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 578a92e522 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 973093ceaa 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards f3f1c9b43b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 71bed2a178 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f8baf9605d 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 11afcf3fdc 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b1535c5af2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 3f545e4f66 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 65bfd50cbb 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards aea1dc2762 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 461452133e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 70ecd7951b 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards a0875e2108 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 604078c5d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards d6bf70032a 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 3671874d07 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards eeb4fc645c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6ab890fdac 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards ec2db6717f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards e39f92b38b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 9143596843 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 65f020e52b 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards ed65c295a3 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 3545ddd447 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards d654fe0abd 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 3c39569c7e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 60c5acc93a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e1c353648b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 11327ec5ce 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards b142b73545 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards a8f582d91e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ceede6a5b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 9af97e876e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 0cd679a3e5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 95ab4eab16 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 0615b03e29 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 2c936cb8ce 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards aa2cdde22c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 1b15163fdd 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 86324a1792 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards c6d44f69ac 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 4928fdb092 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1168a29bdb 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0f75f8d9de 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 7ac6166c20 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 61dec95a18 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 313c1df9dd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3da6167ac3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards df473b493a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 07e228b957 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1b00ad2374 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards a39e8f6c72 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 778cfd326c 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 1c77b03c50 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards db5bd77494 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 8ee9b28539 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards a3bfdcb804 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards bf9e375342 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fc755a63eb 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 5f5a243fca 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e99fe04b05 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards e72d828884 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 1beb5183cc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c406ad1018 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards afa9b44d63 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9afa398da2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ef505445b8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 54dde8ed6a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3f90243009 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c4dfdec98f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e95faca4e8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5cb46f3b05 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards a2519f12c8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 285c14716e 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cae80273af 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards cbb0152f82 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 5faf6b3a1a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 990a99708e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0d2c572f64 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 8f3d875153 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 8eb17d9316 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 095fa54700 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e131d7418f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 69f1b591e8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 43b6e101df 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards d0798f7bf6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards d08a5bfe79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 548ce13611 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards fa4eacf721 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9237408ab6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards f487730857 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5df8561d7c 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards cb8e0ad290 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 283af43ad1 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b86ae5f31c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new af236204a4 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 48b1427755 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new a10e0f2976 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 9d15d3524f 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 4a3a3bb340 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 50e4f9923c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 34eec244bf 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new cc01545b77 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6b96531694 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new cb70063a39 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new be0332442d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new b7a84fc61b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 1e304c58e5 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 60fcc4c09c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 87c7f5be2f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 8ab831060f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2f605e0312 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 14cad5c4cb 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b4ad41c25b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new ca14fd946c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b8bcbdae48 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 2b484ba430 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new e8269cf158 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 69e7e9ed50 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 85e74243f0 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1b378edfab 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 0180d54aba 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 600e3b4976 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 608fa06d0c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 8e56325308 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 11ac2a8f41 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ca3f11775a 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2f3a2d6175 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new cb66b23814 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new dc0ab4bc4a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 32f65c65e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new d9e992468a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 262e44aa41 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 2aef378fbd 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 26e4123d49 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 63469ec0e1 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7bd4fe5718 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 00f7ecbb38 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new cb7c93ef0b 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 064378c4b8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 144da59b22 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 50bca415e2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 53f0d66ebc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 445bbaab2b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7b5f89df44 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a80eafd2ad 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new d15dc63a7d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new f9e9241a10 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 48d7149ea6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 8dd923b78b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 59eefa6c49 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c1ca1be5ce 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 09ab7a85c4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 20bc1186fe 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 116dffebc7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 3ca526829a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 1f24341dfb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new af4e78a50b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new dc3997a021 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 228ac3c777 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new c35372c0cb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 635622b795 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e61d36d2e8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d593c22a67 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new b923fcc188 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 458aa10650 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new eaabd0e4e7 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1c05901069 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 7dd8ae3c5f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new d0353521b9 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new bf4d17a432 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 637befe854 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 8ea7e2c3e4 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 78c2f5595a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 2a4d914f1b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 193ef8e8b3 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 4b76ce3149 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5003621f61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f811aa7fac 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 8f9966a4b2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 4df5395413 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new a05342a463 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 949b5f8e14 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 11f9eb1953 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new cee1ad0451 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 85949951a2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new d136e06fbc 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new cc8affcc78 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 07051fef7d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ce29ca9977 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 04187331ba 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 53feba3716 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 709aea27d0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new e571b6bbc2 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new a73fe56f2d 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new f020a3bd77 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 9a160ecf1a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...]

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 (aff339e825) \ 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31028 -> 31016 bytes 04-build_abe-stage1/console.log.xz | Bin 91412 -> 91372 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 236372 -> 235948 bytes 08-build_abe-stage2/console.log.xz | Bin 228632 -> 227284 bytes 09-build_abe-gdb/console.log.xz | Bin 38340 -> 38148 bytes 10-build_abe-qemu/console.log.xz | Bin 30956 -> 31096 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6080 -> 6228 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 | 25 +- 13-check_regression/results.compare2 | 45 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2662376 -> 2633360 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2199044 -> 2180684 bytes sumfiles/gcc.sum | 2108 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 892396 -> 889360 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216984 -> 216820 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443340 -> 435788 bytes sumfiles/libstdc++.sum | 26 +- 42 files changed, 1241 insertions(+), 1246 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