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 7648b6883f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4bae07c9d4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 14135d3d53 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d10151bd41 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 33f4b68ba1 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards b5818ba815 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards d6e6cdbd62 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 262ff63bb9 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 04d81fe487 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3393a0f742 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 1707806d49 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 90248795f4 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 50f1426006 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards bd0ef2b4ee 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 8e74adad57 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 06b0cae56a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 83b308a1c7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 94ed397748 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards a52451e7dd 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d08f5091b3 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards dbe1acc45c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 20c4ab5062 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 85fe015faf 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4b91a0c70e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 03b6b875dc 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 2951687b18 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards f1da25b218 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 8c1e7d9046 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards c3ded8017e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 762b8fb1ed 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 0d18ee9033 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards e39f8743ea 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 7871016b40 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards d30ed013f6 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 72c585a761 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 96aebc0841 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 6564558f9e 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards b2b4ee206f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0f0d699c1d 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 8bcaab3a6f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9e705a2135 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 12c8b29e2a 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards db7052e94a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards ffc980e0fb 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fddd424347 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 3ab007b090 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards f4dde31721 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 23c5afea07 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 2f60b3a87d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0d38e83c95 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards f205548f71 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ce35131288 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 593c6da656 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards c4c4c71954 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 7b61852fee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 8d02b991ac 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 012adafc8d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d2e2d897d0 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 5a99c02876 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 674a96bf67 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 4ddbf6764e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards e1848c0351 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards feadc89cbd 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards ddc15f0567 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c6625bec67 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 8658e59939 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 5872a01556 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0c29bf4193 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 6514f62902 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards c71631652b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9d0c15b53c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards dc37b52263 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 6ae9dad1bc 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6e5d1e7e70 301: onsuccess: #2118: 1: Success after linux: 16 commits discards c3bbec5c43 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards adb48d06f2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 479c90895f 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards a9671bc509 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards b51f7da26a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards aedf19a57a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 2b44788f98 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 3c08286279 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 3dab3144da 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 2cd3a87cee 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 5530c403c4 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 3d68b5a653 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards f9635cf324 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards ffa6286571 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards cf40d2fe17 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 701a56e8ac 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards ab074430e1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 8ab2931bb6 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 06041aac5a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards b91889af5f 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 5afebd2189 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards ffc19544b4 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 883c4bbb02 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 14518628a7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 4912d77c82 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 988827bffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1e16f4aa70 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new cbb8808726 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new add5856efe 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new addc644f89 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 71d1e4784c 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 047667aadc 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 09a39da940 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 5f60d9b4cc 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 8a589daea1 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 10f6716afe 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new e6c924a279 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new c49dfed4fd 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 99729e871f 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new e3b0292051 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 226bffc646 287: onsuccess: #2103: 1: Success after gcc: 9 commits new d916a7a80d 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new a9b67afeed 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 27bcc7ed08 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 130fafce7b 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 542705ab64 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ba9582baf6 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new faa31e0434 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 38fcf18588 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 927a30fdb7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 0e12e02ed1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 322c31e4d4 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b795fda38a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new f0c07b92dd 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 851675e935 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7475f386c5 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 3c428cca48 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new a84fc40a14 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 68e9e1139f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 4aa26d632f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new a195b24c55 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 5638c84bb4 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 5ffaf63ad0 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 934989e53e 310: onsuccess: #2129: 1: Success after binutils: 4 commits new bca09203f9 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 54a8239ed6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8da6743af9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f2e5d9e7c9 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 90e4967773 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 3f7c239b32 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 62790d3aad 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new bcb023cb54 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 8f969a4b2d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new a0b1a11622 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 0b769093b6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 82476d6327 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 5183326d8f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new e55c107ba7 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 1c20e75198 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6209b23083 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new cdf8a96dd1 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 5886c08b26 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 03e201a0cb 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new c0d1518d87 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new a8a695566c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2855af6bbc 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new a28214cc0b 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 4edfa97792 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5e4634ebe9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new f358e7f8dc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 037e1b1d2f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 19dff4c7fd 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6ad315550e 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 6d86818c3f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 3ba3d20ee5 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 71a535758b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 9baa208bc7 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 0764cb23db 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new ce3f3c668a 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new d77f0d3b58 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 686e619c57 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new a8fbbd59cf 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9711620ecd 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new b52313a056 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a3dbf2ae20 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 787f2c1c2a 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new a0167786c3 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 4db6313191 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 82e007a8a0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 3be662e298 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a8d6febdf3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new efaca7e9b8 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 87f1842418 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new bbc50f78e2 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 649314864d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new a59cb3296b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 56cc15e847 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 5fff3f6e13 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c5b1eafc06 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 4554e619b0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new bb3b0b085f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new abfff5cdff 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 98dedec843 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new a06af9c92d 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new de293b75e6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 100cab134e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e7f4ca86b4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new f67a5785b1 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 27b9aa1ce0 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...]

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 (7648b6883f) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31128 -> 30864 bytes 04-build_abe-stage1/console.log.xz | Bin 91784 -> 91456 bytes 06-build_abe-linux/console.log.xz | Bin 8616 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 237412 -> 236256 bytes 08-build_abe-stage2/console.log.xz | Bin 228436 -> 227556 bytes 09-build_abe-gdb/console.log.xz | Bin 38512 -> 38064 bytes 10-build_abe-qemu/console.log.xz | Bin 32108 -> 31868 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2892 bytes 13-check_regression/console.log.xz | Bin 7328 -> 6292 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 44 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 154 +-- 13-check_regression/results.regressions | 40 - 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 - sumfiles/g++.log.xz | Bin 2656784 -> 2652092 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2222284 -> 2219936 bytes sumfiles/gcc.sum | 2192 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 897312 -> 888348 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214344 -> 214460 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443996 -> 444076 bytes sumfiles/libstdc++.sum | 26 +- 43 files changed, 1230 insertions(+), 1554 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