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 66d0d55d78 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 3a3a5f7b53 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards af4649a7ec 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 80a6c2084d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 712c184481 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 111b65dbab 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards d7f2c2fdc5 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards b99f472648 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 15e3f94044 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 1c33d08aab 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards cec445fffd 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 9f57f574ca 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards d914567dee 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards be48d0ce30 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 7f55aaed70 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a3f97b85b8 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 87723c1428 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards b49019a1b8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 2dffebb248 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3fb0e20a2d 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 66cb6acade 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 03c0da3527 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 7f4b4c53e9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 79aede5ced 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards bd8419e81e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1bd254074c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 31d38d6d57 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 54a42e3c0c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 3d5392268d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 3c4221c5bd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards b48197e986 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 83eaf59629 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b215f6bd4f 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards befb52311a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 5cbd576171 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ac1252f58e 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards dbac275ab7 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 255f6c0013 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 1bd690006b 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 1069e85975 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 69364f8d77 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 79be6f360a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 3cf3db12ac 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards b6242e2082 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 0315e854e2 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards a12b9ba3ee 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c4c7c9fd9b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 846f216f31 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 12cae726d4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f36255d2d4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards b04780f961 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 093d078679 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards d8f4d5dfa7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e6ac1fed1f 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 6d026cf08f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 31bc439bf1 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 2976afc8ef 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 19e0a15a03 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 8fb368eb68 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards e253f88367 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8622b03be3 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 7cfe6ee3f0 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards daad9be35e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 1b2e953c79 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards dd2e747123 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 487e3e7cb3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 9c820d9a86 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 939c7107b0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 7ca193a2c4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards c7c43c6a0a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 8e2b01b8a7 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 1088f0e449 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards dd27a09f22 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0afd6512de 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c0245c3271 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards e8b3b71c38 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards f1887431ba 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 03e3a440be 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 03019fa6fa 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 15b63f170c 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards d54d49f07d 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 86fa7ada50 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 6f195aa713 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards acf937629c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards a2fb925b6c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards f54c10f4ea 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 663556afd9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards c9084a4821 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards e89b4dc58e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 62689e0d17 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 8d12691a1a 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 37d7e1cb8a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 875f9bfffc 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 897d36b909 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards fb426c5271 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 3639023ef3 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 0411241b2c 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6587830124 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 912b43f4e8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards e3f106f1eb 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 1eb0bbbe61 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 91997c5a3c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 5b44172e85 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new b34b6d6891 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 74912685ef 287: onsuccess: #2103: 1: Success after gcc: 9 commits new a6fddb80d3 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 7a0b3704e6 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 240228d3fc 290: onsuccess: #2106: 1: Success after gcc: 2 commits new fdfd531741 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 5a83255ae6 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 22820f3b2f 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new c434e0c3c1 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 6a0b8160f3 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 57d7f8ee15 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new efa317cbfe 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 962998eafa 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new dc28e0341d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 3948163519 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6b3ecc65b0 301: onsuccess: #2118: 1: Success after linux: 16 commits new 14f322f1be 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 866919f534 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 303bbad820 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 833f87817b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new fdfc89908b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 57cac97788 307: onsuccess: #2124: 1: Success after gcc: 2 commits new fac43e4415 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 23a47eeccd 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new eb2bcb20e6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 01e07357ef 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 034c35973e 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new e8c7044e10 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new cecf117430 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 8df69a0d68 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new ed2e2a9387 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 25717e7cf6 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 343e2ace52 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 415df147d3 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 88c387b527 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 04fe04d1b0 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 0a52ae222c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 379c67c4bb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 979977805b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0dec8ddbcc 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cf31e8c93d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 7ed84e3bfb 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 74d4a4d1cb 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 323827cf9f 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 541cb4f033 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 63956428db 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 068cc4c3a2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 0e74ad8bc3 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new c2fe4fa505 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cd957f29a2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new cad99715b0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 39e8e3943c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 8bcd2a3cee 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e61cf39570 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6810e263f5 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new b8a5eadfcf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new d773364dc9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 75c5009c4c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new bcf5132f8e 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 2c291bc94c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 07091ee804 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 592658d87c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 945d992acc 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new dc0f6dd717 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 0160ddfc82 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 4042a503ba 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 1d8b1af246 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 30b14efb99 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new f322357658 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a58865637e 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3437756c5b 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new fb0d91b28a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 9433b93622 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 6ccd72faa1 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 6f828eccc9 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 874411c6e5 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 3045043e58 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 0cf3a54505 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 77a46b9c7a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 5da4e94d12 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 17f0bb349e 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a38a081668 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new da5d8d28cd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 3180aaa3e2 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new eb862df7fc 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new c0a5ee964e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 114f0cbe24 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4447af5636 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 59c82552f5 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 9b637b7bce 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new f48668e7bd 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new c111b41f48 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new ebd77bbbdf 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 10d41a2e6f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 257e7f75bb 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 69b329ab0a 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 1e961b6657 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new c0759bd5f9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new edea598973 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 08ca244e02 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/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 (66d0d55d78) \ 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 1808 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31044 -> 31136 bytes 04-build_abe-stage1/console.log.xz | Bin 91760 -> 91436 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 236592 -> 236824 bytes 08-build_abe-stage2/console.log.xz | Bin 228256 -> 228224 bytes 09-build_abe-gdb/console.log.xz | Bin 38304 -> 38548 bytes 10-build_abe-qemu/console.log.xz | Bin 32120 -> 31908 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2968 -> 2800 bytes 13-check_regression/console.log.xz | Bin 5768 -> 6624 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 | 9 +- 13-check_regression/results.compare2 | 71 +- 13-check_regression/results.regressions | 26 - 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 - sumfiles/g++.log.xz | Bin 2637628 -> 2633792 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2211280 -> 2185500 bytes sumfiles/gcc.sum | 1820 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 891932 -> 888268 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214556 -> 214416 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435976 -> 435448 bytes sumfiles/libstdc++.sum | 40 +- 44 files changed, 1087 insertions(+), 1150 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