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 7221c3e25f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 8ab7d7ca43 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards a6f3a55155 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 52f7f1ec53 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 75efdf4182 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 27415b6969 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards e39f4ebbcb 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards a5dbc4f2fd 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 547687e00f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards a12462fe05 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 76c3f9493e 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards cbb0490d33 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4b81e3103d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f950f4ac37 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards eb6b1d5030 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 464e4a1181 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 4ebde4aee6 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards c3437d4588 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards f92177cdd6 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 0b27233abb 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 4c9ba07805 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 731aa802f0 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 52804fe0ee 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 9e35a804cb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b394f8e03e 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 11a22f16dd 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d55dca8758 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 5c17bb3f2b 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards f4d3656b2c 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8baafa13a5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c7243e8131 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 4f8f516ed3 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 0366cd30ef 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 337610b9d2 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards abca45845a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 63155e4056 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 3d8d157031 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fa82ff37a2 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards b8f765241c 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d6c362a8d0 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards fedea84793 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 0ea1979bd4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards f38e7a926a 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards cade27172a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 00fce40555 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards bcda91816a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 4547c6fc14 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 5bb7a75454 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 87c1310529 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6a4a2e765e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 48cc47bcdf 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e72edc6380 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 22e03d8a61 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards dffd1d4608 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards f6d21826ae 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ea9ea0336b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d093187ed1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 05d635d23a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 1d7d03c954 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 034bc8652d 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 310eca8ebf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards dde7512789 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 2e5d4907f0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 091c86333b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 115a0b9473 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 984082b85a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ca66850cc2 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 00423c094f 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 5d24ae3529 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 717f9c0a75 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards d5f883c426 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards a6922a0a70 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f52543a97b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 5bfbc378b1 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 65ec8b2ed9 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 6404ad9a99 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 7c29e8bbb7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 64b54a8cfc 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ecaec3d5b7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 6d55919ce2 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards df331715c9 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 2801c59f7e 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 0350e182cd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 4a213fd9c5 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 8d37122d3b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 65c982199d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cd002a1152 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards a1b5d7dd76 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 2bafcdbe8e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 9246697993 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 84ebd56613 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 07598b6f4e 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 2b097d6d76 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fc7c85422a 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards e98c4bcfa4 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6674719324 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards a35d4d5aa1 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2c46916a85 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6ad68ad41a 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 76aea855be 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b093fb78c6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new f292acbdd6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d481e9bbe6 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 68abad3dff 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 3897023cac 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new a46fc9883f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new aadac72e99 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 4955c368bc 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 97ef8a0312 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6a8621d5aa 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 41e06da79b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 3f343088be 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new c37b47c4da 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 3672c8687b 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 910e8cf532 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 8bac8553b5 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 5008f0d809 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3309bad612 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new f8cb46e44c 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 7070a87729 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 240c36ea43 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new de1a011d3b 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 2fa5a95334 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 95dcf7a179 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9bfa0c813b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 8a48e6bfab 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new bbc9693e5d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d75941804b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 314f0fba90 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 21610718c6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new d53639996c 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new dce93d3025 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 09c9176401 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c16f3ade75 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 3f57d57c7e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3c7a46b368 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new c2b27521c3 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new ab89431d12 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new e801081b1e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e8a5205926 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 82399af005 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 381b10dded 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 3760585e6c 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 5281dcb0af 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 1b21bc7535 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4181954622 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 9c65ed1d24 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 632ffe2f6f 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2518087576 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 7a9cf8dae4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 2e42531fa7 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 2a0916f1b3 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 3dab253b8b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 88ff5984a4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 72871ae79d 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 0b25f38ddb 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 9244165a26 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 80d4247eb3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 37c24e51e4 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 465bce28eb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 62eea2367a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 5f5777a423 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new bda996c9e1 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 50214a179c 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new f8852a48dd 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 92b621449f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new e50e1d13da 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 79283a421e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 80f6705aa6 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new e9dc9776f1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1e782e5365 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 3f1be86e8f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new d0755f1bb2 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 2d1d42bbd1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9d71b792ec 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new ce7748ac3c 384: onsuccess: #2205: 1: Success after gcc: 2 commits new cac7dc150d 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new be70753388 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 53527e043a 387: onsuccess: #2208: 1: Success after gcc: 2 commits new ea71827080 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 75fcc4a285 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 14ca5f3197 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 6edf1c9ff9 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 61ef3e7ef2 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 8f007dacc0 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new d0eaa90d1a 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new de088c305e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 4e59198449 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 576da713d2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 59e35530b4 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new efe2edfe45 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 99522919d7 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 3f56766078 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new c84c48fa21 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 98511389a7 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 8428c8f2c0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 2980733413 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 1587529d35 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 10061a5f9d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 25a84d0936 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new cc9b0bfede 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new f0fff08d58 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 219ef39e4e 411: onsuccess: #2232: 1: Success after gcc: 3 commits

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 (7221c3e25f) \ 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 1760 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30912 -> 30912 bytes 04-build_abe-stage1/console.log.xz | Bin 92040 -> 91688 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8932 bytes 07-build_abe-glibc/console.log.xz | Bin 236400 -> 236652 bytes 08-build_abe-stage2/console.log.xz | Bin 228184 -> 228160 bytes 09-build_abe-gdb/console.log.xz | Bin 38344 -> 38124 bytes 10-build_abe-qemu/console.log.xz | Bin 32184 -> 32648 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 3056 bytes 13-check_regression/console.log.xz | Bin 6844 -> 5184 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 23 +- 13-check_regression/results.compare2 | 41 +- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 40 - sumfiles/g++.log.xz | Bin 2650768 -> 2629296 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2213672 -> 2223852 bytes sumfiles/gcc.sum | 2516 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894548 -> 897324 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216840 -> 216984 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442152 -> 442036 bytes sumfiles/libstdc++.sum | 24 +- 40 files changed, 1375 insertions(+), 1570 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