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 ad7835c275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9fa920fbc1 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards ae6c03a58c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ce94c84015 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 0fe7265970 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 084c8bea55 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards d943b2d137 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 76e617472c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 87aa472244 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 2f6c095734 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 4fbb25c4a2 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 49eb57d928 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 7905a69452 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 0b0d48d0c1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 34f2507d56 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards b67c46ee59 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 29256a1ada 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a10bb00197 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards b9eede0ad4 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c819e5011d 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 79973bd3ce 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 06144580d1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 353c376d2c 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 8e0ae871d6 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 5fed159209 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 9b41a732c8 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2a2112c9d3 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards defcda6d53 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards eb6c47b95a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ad39ef1463 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 00bfb8203c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 58739e9067 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 6d0d9b19ec 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards cc5b4d086d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e15271bf63 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 02edc3aaef 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards d223030b16 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 4becb8a471 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a6b6c32b97 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9630acfad3 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards daed8d1463 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards a1a04df0af 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 00d5f649e3 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards b467c49fe4 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 01f22e56c3 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 2cf30786a8 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards a40edd813b 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 3b95545132 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 05b8e07158 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 32cd6c671b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards bcab69df1d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 0a5e29b306 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 450e6638aa 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 2350f9244e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards ccdb6659e4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 423cc136cc 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2d10320220 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ebca23a63e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards f5d9e98a26 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 8e75379819 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 192ee8b633 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards c9e888e244 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 040031211b 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 745ec88705 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 89aba5ff87 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 2b9eb5d16f 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards e50509397f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards d9240b274f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards c1d559c88a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 75a845b69c 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 17c788964b 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 988f69423b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 12cbaa4883 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards e565441b0d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 4cf9499ed8 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards e9a741f895 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards beacf3d495 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards a7d170c22f 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 93041fb90e 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards fa4c1bc6d7 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 55e23c282c 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 80594229a6 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 005d3facca 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 59897e98cf 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 7284ca1105 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards ba0dcd4bdf 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 6e3f341e2e 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 98b4e70356 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards e96572125e 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 9e37e65eb8 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 5bf86f2546 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 9efadeff31 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bb5cdaaaef 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards eecadeebc4 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 679745a2bf 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 4c180629d0 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 850d74d92f 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards b0d548a39b 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 3fcaa36307 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards d0903bbd75 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 3ff58db684 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d0fe365bc2 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new d164b31494 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new cd39f6403a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 5f1e15e42f 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new c0197ace4c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 59a4a2fb34 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new cb8cce3145 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f40cfee96c 259: onsuccess: #2075: 1: Success after glibc: 2 commits new fd40f3ded0 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 6a7d08aa09 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5482c101c7 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new f6815c99ca 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 292f1be58b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new b3cf99b57f 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 3080f4ab3f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 7f1f1dd62a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new b7c47dea38 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 606f344c2c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 12e6ad540b 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new d68bd21bda 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 9752ac849e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new f36346c5bc 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new e8521a3a2a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 3c4f6497ef 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 260a24758d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 39bc5e9cf7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 48fb606573 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 402d71e751 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 4a63f816a6 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 3e4fafe548 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 1dd02434f7 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new f8691b543b 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 5b8b8df07d 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 114a2377b1 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 00afd88e76 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new ae8348240f 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 3747081052 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new b79e480f19 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new db9c813656 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 7b673f0b1e 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new e30e52bba9 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new b604285ab3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 5029b3a22b 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4a8fa53af8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 25878bd7f2 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4bba4f2406 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new d4671f6601 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 376014573f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 81571f6656 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new e113bbccdb 301: onsuccess: #2118: 1: Success after linux: 16 commits new a7495bd211 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 82dab11056 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1bf4224569 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 08bd99862b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new b1c740af36 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new e2f579ac5d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 2dba1011c6 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 6f7b7c5cc0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new e3fc8edbb0 310: onsuccess: #2129: 1: Success after binutils: 4 commits new be35cc2897 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 98b9740d85 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new ef790308e8 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 429f5b3859 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4e6a2ba6f2 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new dac956f779 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 491f1bc6ae 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6a2f0d1fab 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 641f382f18 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new bbe06a1e0e 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new ccdc3b9f7e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b21319372c 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 9ca9dceb49 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 81ea259355 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new da455c7e7e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 75814287c9 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d6ac12ddc2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8792cce1da 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new aaa8378978 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bd126979ff 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 688c4323b1 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 5e665521b5 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9576cf4264 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 6fa7409453 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new acbdccb50c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d90604c7eb 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new fff0a4f88a 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1ac3eccc38 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 434a3b8eea 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 832b817f66 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 0cbcec8abd 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new dbcf8397ff 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 4e24a2dab0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 4c7a1f0e20 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 35c6767f2a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 5434ba7116 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new f14ea69936 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e28c724f07 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 95da556c09 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 432cc52821 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 91a4fc911a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 953b3397bd 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5ae7ff64a9 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...]

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 (ad7835c275) \ 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 1764 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31820 -> 31544 bytes 04-build_abe-stage1/console.log.xz | Bin 92048 -> 91952 bytes 06-build_abe-linux/console.log.xz | Bin 8992 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 240168 -> 236496 bytes 08-build_abe-stage2/console.log.xz | Bin 229016 -> 228620 bytes 09-build_abe-gdb/console.log.xz | Bin 39204 -> 38908 bytes 10-build_abe-qemu/console.log.xz | Bin 32160 -> 31924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2592 bytes 13-check_regression/console.log.xz | Bin 6452 -> 5620 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 | 21 +- 13-check_regression/results.compare2 | 42 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- 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 2692288 -> 2692108 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2241952 -> 2245452 bytes sumfiles/gcc.sum | 2156 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896920 -> 895432 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213988 -> 214048 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 445344 -> 432016 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 1209 insertions(+), 1299 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