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 dcba9c120f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 4c20bbcc75 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards fc0a1e375b 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 55c08af12f 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards ba0becc269 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards f94a1dc72b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards aace75ac77 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 728ccf4ab9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards df091d9fb3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards ec4d6d767f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 01c9a33c82 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 6a9e95a590 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards fc0cc2673a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards e14dfb30c2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 96c218b75d 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards b53cced8d3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 08a39584b1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards cac9396ae7 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards a09654c26f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards ba6b121a84 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards ebfd52165c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards d4c03a7e8e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards f04e47921f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards aeddfb361b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards a473bc7cab 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards aa470448be 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards b26d9af017 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 83ccfc56c8 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 027fc176ae 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards f2088c18cf 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards cd9f7eb5c3 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 03efe62e92 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 83616bdc34 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards bd2ffa68d3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards a7fef0718e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 7264bdc037 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards b89dd1185a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards b67d5908bf 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards d0c50ece43 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a07395e783 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 67f2e4a8d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards c71f75d2f7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards bc0244ade8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 1392963447 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards b378eded33 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 51c17f5d8f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 333218f72d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards ee58347199 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards bc5cd3755f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 6c74d52c55 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards e0cc8bff1c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards c35bf15f7a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 96d35fd18b 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards dabdab4d46 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 04a46de034 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards db6f8c7df4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 220e195c1a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards dd0f1e5399 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards fba47f1cc4 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards aeae356534 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 1ff192f746 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f87f971cea 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards fbf6c6d249 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 2e101dad29 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ebe78d54c2 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards a33a8e395f 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 1112ed54f1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 4920075db7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 01ffe69fab 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards bcde344076 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 2ee8d98633 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b6287e386d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 29e30a419d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 4b502722bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards c980ed00e2 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 44b143b11a 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 73cd42ea94 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 9485d97196 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards a750cf51ae 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 2ff49294cc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards da71d97122 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 07127089cf 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 2291fa8554 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards d0a2c7f706 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 170f82179d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards fc87e53659 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a429691b7f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards a497e6eeab 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards bf0a406735 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 15c3fcf8cb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 4a2ab8ce57 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 3249e156bc 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards facfaf5df8 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 125d151889 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 8a6accfdbb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 4d99fb18b8 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 04674562eb 295: onsuccess: #2545: 1: Success after linux: 10 commits discards fb0ca36284 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards bde0fc0cdf 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 533fce475f 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards cacbda0775 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 52d9dfef13 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new b9321c42ff 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 363f04141e 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 493b4d96e1 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 4c19afc331 295: onsuccess: #2545: 1: Success after linux: 10 commits new ea05c41682 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 26d6dfe74f 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 2b9420ec64 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 002b5cfca1 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new e2a135e620 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 5437a71f7e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 6ceca6d1bc 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new dd8b3b0f2a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 5b17a33355 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 0f13bd709e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new f433d36689 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2cdedb17d8 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ac33a5a469 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 728c3a1f41 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 06563524df 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 5bb720906d 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 39b93c4849 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 179bd1c755 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 4b20e221dd 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 8a06134e74 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new bea0d4d460 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new ab4a058dfe 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 14022ba143 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new d5c2cbe361 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5db3881a2e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 718ca49e47 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 89297fdf1f 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 6d57f682b3 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 9f6e2960c2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9f6bf8d253 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new f1729e3d81 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 549c6f4a08 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new d37f5a71ac 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new b4d09e4cf3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 918b769835 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new cc6d2fb8e9 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 7e97fb6531 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 2a107a6c21 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 60b1d24e4f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 57709eeb1a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 6c9d5db084 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ae83929b64 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 309bf427d1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 7a19e11fe8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 33af449572 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new bdaa08cef9 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 650d3cd053 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 0577070964 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 551b6a2971 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new b6f8c013a2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new a49930b84e 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 273a6c9ceb 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new a26ce1da1b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 344c3afdcf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new b515679fd1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 6d3a974be0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 526a816616 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new b0340305d1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 2c280cc53f 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 092c8b28af 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 3176b95606 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 8a20661e30 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 08c7d807c1 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 0e68abf445 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 376b63ec71 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 3ab5f97534 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 470786b8c5 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new ee9a44167d 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 994858f28a 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 109f6d0594 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 9bba18e2e9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new ff0e533a12 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 774dbc36fa 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 1a4375f4af 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new db83092faf 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new e273214476 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 9c5c2bd8a6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 6851494bbf 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 336db6b724 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 164b25aca0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 515c395c10 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 7eeec0f21e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 1a8439a779 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c7a0318abd 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new eed74caab8 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 1295d3a1a3 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 3544c0fb5a 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new df339735f8 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new ab1e91a63c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 4792968129 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new acca97576c 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 8db555b141 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 466c38b414 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new b0885bb454 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new b3d2dce0b3 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 4234047b44 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 6e3a3834e5 392: onsuccess: #2643: 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 (dcba9c120f) \ 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 1800 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31184 -> 31160 bytes 04-build_abe-stage1/console.log.xz | Bin 72888 -> 73348 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 244556 -> 245328 bytes 08-build_abe-stage2/console.log.xz | Bin 204244 -> 205208 bytes 09-build_abe-gdb/console.log.xz | Bin 38460 -> 38468 bytes 10-build_abe-qemu/console.log.xz | Bin 31348 -> 32352 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 3192 bytes 13-check_regression/console.log.xz | Bin 6316 -> 7940 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 80 +- 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 120 +- .../results.regressions | 81 +- 14-update_baseline/console.log | 64 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 55 + sumfiles/g++.log.xz | Bin 3376764 -> 3411724 bytes sumfiles/g++.sum | 28 +- sumfiles/gcc.log.xz | Bin 3022220 -> 3016088 bytes sumfiles/gcc.sum | 6271 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1039484 -> 1040308 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217532 -> 217612 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434832 -> 437736 bytes sumfiles/libstdc++.sum | 42 +- 45 files changed, 3577 insertions(+), 3417 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (79%)