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 8ce9b13dbc 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c953812402 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 4592443500 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 7872a29d69 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 72aba17930 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 3968f2152e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 2a94159467 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 68876698e9 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards b34394542a 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 1e053b00ab 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards c567f0329a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 208f7cd5d6 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 96a1913a88 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d935089267 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards a5b726444a 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 8d959a5d43 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 241f19f9c6 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 929f470ecc 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 3baee8453b 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 0f6520f907 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 5d1f11eacd 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards a02943c885 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards a430551f18 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 9c7a976fe1 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 0f682c6978 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 36fbf5b75a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards b749443807 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f5952fa28d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ab0304e77d 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 4837288ae9 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 3f15937f54 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 37adbcc3e4 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 89a0d5ab8d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 7d4b7938b8 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards aaf6b9bab1 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 0ef3c76de2 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 5ff2730124 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 97d34448b5 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards a450f0e7d2 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 0f290e6203 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 674387fdc4 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards fe8b11159c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2a1e6b30df 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards f11bf96a26 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 3e1d714549 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 28c4788e76 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 80ca00abda 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 61d7910fe0 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 6a99279e18 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 7661c1ee8f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 80ac09f55f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 62e5c030c2 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 6ecec43b8f 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 5f88f436d9 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards e494126d21 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 7dd8cef8a1 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards b92b6de992 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards a97dee738f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 4dc669cdf0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 5e2cf6b022 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards c003fd3d2a 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 1d06723eb8 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 50eef89c4f 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 71dd563004 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards cb83f4864c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards a96579e896 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3369c65103 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 6d44bf823f 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 592f68a44f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 4e5e5bbcc3 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 875d3ed856 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 13b63dbcc8 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards c2b1813ca2 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 94f199e200 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 50643c7fee 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 4a8f88205f 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards c305a8d04c 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 801e40eb2a 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 9f024f73ac 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards c9ee4c75bd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 798f74eea2 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 7eb551071a 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards d1377f8049 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards da49f65f81 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 64bea2addd 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards f036fc1a27 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards c569c3893c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 924166d38d 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards f26ed3d041 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards ec05fb9df1 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 2a0dec17ef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 3d5391fcc7 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards b3a677c737 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 8835a85786 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards b73a1de962 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards b43ae544ec 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 84d899387e 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards a4f1051908 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 8887c52d69 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards c8cc22556c 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards a4b3a66744 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 2a43710cf5 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new f3fa20abba 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 81cb29b562 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 716b9b5603 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c8e95bc6d6 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 97f96a2f84 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new dfcd2aac74 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new b1744078bd 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a6e1444f43 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new fa1b2cd957 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 40bc831426 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 89353cd2ee 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 1823c031d8 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 61e69a3624 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new c1a9e42ca4 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 4e7d14ec2f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new eda76bcb42 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 5984340f87 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 77d872e4d8 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 4938996b22 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new b467583afd 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new f505181261 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new f5e2d10da7 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c32f91d85a 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 91454d7897 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 1f404ea0b7 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 53c34d1df9 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new f7f991ac79 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 9e5f4b22ab 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new f7860740ce 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 7b8cefb7bd 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new fbdc470ac2 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 00fa42c550 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 2f9bc6e935 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 80818fe4b6 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 24f42450aa 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 942e1d593c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 714871acec 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d26085e968 293: onsuccess: #2542: 1: Success after gcc: 5 commits new eeb8e426cb 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new eb0c7df530 295: onsuccess: #2545: 1: Success after linux: 10 commits new 28c91f67a6 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new ee488c2ab2 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 750ad9f54c 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 2828717dba 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new d9dc5f05aa 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 31844c77e5 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 116809b969 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new db7da1f944 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 91b264a7da 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 3ded3b4cbb 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new fd47e431d9 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 864ec3a2dd 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new e101eb23f8 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 29980e0406 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new d727cd3aec 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 0b1a950cd6 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 807235e8b1 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 4a749842ea 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 0ccd3856a2 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 8d6b6d8c49 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 5202d8ab76 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c610770bca 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 5275a6de59 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a4b3979c12 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 00948ae35c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 099755b3ef 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 18fce25313 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 66600c2367 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 2b98cc5bc0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new abdaec1967 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 792352d173 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 2c6b5402fc 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 95672c5a71 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new d45679ef23 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 3d62879519 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new bab9f11c2e 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 97f3bc18ae 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 33e3fac87f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new c2ee6e1f47 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new bde185a97f 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 2b1405b03b 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new aa182adcf5 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 18f8877798 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new d6c4ce80fe 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new decc52d290 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 7cdc7e431b 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 35649d22d9 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 2f0956399b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 20f23def28 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 675935c9bc 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 4418e9cdbf 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new f2f1a715ad 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new df98051a8c 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new a16deb24cc 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new bed6ba8666 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new bbb78ff7e6 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 1159d690c0 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 7c41f80f37 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 8f1da80509 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 251b1e5218 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 613e3ee341 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/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 (8ce9b13dbc) \ 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 1756 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31612 -> 31704 bytes 04-build_abe-stage1/console.log.xz | Bin 74280 -> 74204 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 245640 -> 246524 bytes 08-build_abe-stage2/console.log.xz | Bin 208484 -> 207536 bytes 09-build_abe-gdb/console.log.xz | Bin 39044 -> 38812 bytes 10-build_abe-qemu/console.log.xz | Bin 32200 -> 31656 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3972 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2968 -> 2996 bytes 13-check_regression/console.log.xz | Bin 10716 -> 9504 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 105 +- 13-check_regression/results.compare | 62 +- 13-check_regression/results.compare2 | 1356 ++---- .../{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 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 107 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 47 + sumfiles/g++.log.xz | Bin 3395872 -> 3398972 bytes sumfiles/g++.sum | 59 +- sumfiles/gcc.log.xz | Bin 3015216 -> 3031364 bytes sumfiles/gcc.sum | 5100 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1036084 -> 1043048 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214852 -> 214960 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429400 -> 436984 bytes sumfiles/libstdc++.sum | 51 +- 44 files changed, 3263 insertions(+), 3929 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (51%)