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-aarch64 in repository toolchain/ci/base-artifacts.

discards 900d145160 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 6de502c9ae 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e9dcb80984 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards afcf12dece 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 869033954b 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 65921cd0bc 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8486f3ecc9 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards b7e6837c56 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 60fba0ada8 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards f48284ebad 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards b75f801120 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 667f991696 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 440cd2992f 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards f2ea21ae84 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 1b375e0df7 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e8dc8df637 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards e5c12e90d8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 95c78fc92b 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 572e1af011 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 6e986aeb79 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards ece9b47ecf 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 901cc25cf4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 451a084820 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 82954122d3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 3659101a6c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 8951f36c75 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 8fee7ef138 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards f27aa0c08f 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 845817fc60 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 503a707970 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 130a6c0c46 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards e4e857a6ff 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 424de00f68 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 33d29745f7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 6775946de8 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 034202b8db 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 465b9198f6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 7149b09004 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 5304238854 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 0f280aa03c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 4d1fa534bd 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards be9bf10939 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a78cccf2d5 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 388d89e69a 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 24c7e4afc7 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 9e8277115b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 0b37f87a0f 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 0ca06d3c74 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 9f943dc0d1 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 30c70c92fd 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards c764101d2e 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards c22e9ce858 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards f02423b28c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 0b9e423fff 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3ac23134c6 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 7fde4bdd5d 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 93dd222be5 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards c7f63a870d 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 0ea8616d4a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards bde066e4aa 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 747d2cd3d9 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards effb65a6f0 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards e65710abfb 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 2392cc69f2 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 437e28a047 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 3fbea6c4d1 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards aaec7677c1 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 92abcc3df0 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 671318c12a 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards e55afdbe91 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 8716c2fcda 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards d25f825444 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 9de3fd9e9e 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards b31519ba59 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 8c6ba3624a 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 68aed0f3a5 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 11b6c4bf13 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards aeab3b301f 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 9cbe723833 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 3f256ffe88 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 60580f4a19 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 8fa8e4bd73 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 24cf0ee9f1 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards a4f64e9759 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards f8d42b4bf1 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 3428810814 235: onsuccess: #2483: 1: Success after linux: 108 commits discards b232e2aa0e 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 3d0d31a75e 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 4cb247921d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards f48c354028 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 3451047ff8 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards f956ee5151 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 930706f15f 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 45d6a4ee14 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards bc2dd5941c 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 9694a993d6 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 176a93907f 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards af1a297aff 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 2f94f5386a 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 1ffc2cf7be 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards f575bfaceb 220: onsuccess: #2465: 1: Success after linux: 572 commits new cfa05c67d0 220: onsuccess: #2465: 1: Success after linux: 572 commits new ceafd904a1 221: onsuccess: #2467: 1: Success after binutils: 3 commits new ce5a7956ca 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 957ed5e284 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 388e7d18d2 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new f9a31bc6c9 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 176fa1c6ae 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 94b92ca595 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 14581e44a6 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 42d1e5a49a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new e09456187e 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new a10b555d0c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 5ba7979146 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new a5e00c49b1 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new c0490097e0 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 024e924ebc 235: onsuccess: #2483: 1: Success after linux: 108 commits new 6a4a224b26 236: onsuccess: #2484: 1: Success after gcc: 2 commits new a93172dce8 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new b58f7247d4 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 3feaa893bd 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 7099bed67e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new faad2e4245 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 8ea185bbc9 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new f6ce10f3f6 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new e7fd791243 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 8d84093e26 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 06211f0725 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 259f1254b2 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 463a5c5928 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 721d85db1c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 323e00ca7a 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new a3b96e9e0e 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 8ebb761f1e 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new d1aa9ee7db 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new a389f258fe 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 41a63afd49 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 0e55ace345 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new f11218ba7e 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 001ae886ce 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 9d27f9bf2e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new a76f179f09 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 491fecad82 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new eca8272e4e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 5e8eead0dc 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 424eca0e35 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 738097a81b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 3110548b6a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new aa311b203f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new a68d5ed779 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new cd596d658d 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new b7bbb77b73 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new fb90074526 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new a12cd7059c 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 0b52b29f1a 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 40dcaa4f60 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 784b350fea 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 1da4fd7691 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new e4da4a24f1 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 38e451b7c3 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 1e56d60a10 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new cbce6c6240 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 110a963fa4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 6e251e4301 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 73f1cecdbb 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new cbc4ce7d8c 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new b662a1ffa7 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 3a0236386a 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new f059b9d5dd 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 154febeb0d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new acbfd80a64 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 371034fa7b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 36cde0a10b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new b77fc4eb9d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new ef91d4d887 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 4253691e51 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 3880462b31 295: onsuccess: #2545: 1: Success after linux: 10 commits new e25dbb1f41 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 1ebf32e0b1 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 5144170cda 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new e4da5449c7 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 00cb549d60 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 225afc7c42 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new bdcfe8afbb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 2a44ec4aae 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 831a8fbaed 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new e599c4c45d 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new b4367fa0cc 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new d0b4f959e0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new bba2bc6d8c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new ef0e2a3d3c 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new fd011b177d 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 51a99248c2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 8f9335549b 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new be7702ad87 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new a435814e7d 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 51eccb1fb0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 1b45fc3863 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new dac9366cb9 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new e967e5de44 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 194aa29784 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 77a25891a5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new bfc519bc54 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...]

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 (900d145160) \ 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 1792 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32524 -> 31992 bytes 04-build_abe-stage1/console.log.xz | Bin 74256 -> 73264 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 247180 -> 244532 bytes 08-build_abe-stage2/console.log.xz | Bin 207680 -> 204480 bytes 09-build_abe-gdb/console.log.xz | Bin 40008 -> 39472 bytes 10-build_abe-qemu/console.log.xz | Bin 31392 -> 31780 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2844 -> 2624 bytes 13-check_regression/console.log.xz | Bin 6836 -> 6292 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/{results.compare => fails.sum} | 45 +- 13-check_regression/mail-body.txt | 97 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 60 +- .../{mail-body.txt => results.regressions} | 106 +- 14-update_baseline/console.log | 70 +- 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 | 99 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 48 + sumfiles/g++.log.xz | Bin 3437952 -> 3414232 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3023876 -> 3036908 bytes sumfiles/gcc.sum | 4618 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1044316 -> 1043520 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214728 -> 214760 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2700 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435760 -> 428532 bytes sumfiles/libstdc++.sum | 6 +- 42 files changed, 2629 insertions(+), 2659 deletions(-) create mode 100644 13-check_regression/extra-bisect-params copy 13-check_regression/{results.compare => fails.sum} (50%) copy 13-check_regression/{mail-body.txt => results.regressions} (54%)