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 5823b418ce 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 68bbb8b989 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards d182cb03d2 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 5cf3764c0b 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards 50f5bf7759 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards e44fde9b6c 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 1272f5671f 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards cdf42034b4 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 8df8c36baf 427: onsuccess: #7: 1: Success after linux: 26 commits discards 5909acd44c 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards d016ed0fc8 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards cbd0fa4aa4 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 61a6e555d1 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards f631a014f3 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 3316668603 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 516dbafa68 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 1195c49cb7 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 69ef0e41c9 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 9e2b5747ed 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards f6f2cdd58a 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards ed57f0af87 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards b2bb000835 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 8f14ba744d 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 29eb71bcc1 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 4a3fda70f4 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 1b96aed5e4 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards b2d0ceffb4 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 7210be9514 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 45f81cddd3 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards dbb6fc8fce 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 9deb009851 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards d8b705aa05 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 29ab0f3202 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards c615c1a4e5 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards e5e785543f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards c7d6796772 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 921da06efe 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards d76f826c49 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards c908d544a9 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards b219977f55 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 701ace3396 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 0abe177059 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 667479602b 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards fcaf237a7f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 1c1790608e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards ce7f5027a5 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 68c5365ed0 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 08f8ef094a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 0f9cc4453e 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 2c12c5562e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 47c02865f2 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards c603af3ba7 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 98a5472db4 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 11f06bc0a7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 27fcea84db 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 7ddb7ef5f9 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 1d88538509 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 3d51a93a37 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 6913b58c03 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 9309caf2af 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards d32d4a0807 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards b183cc8e89 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 5ffadb76c7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards e7fea23bf0 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards c12de38400 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 90e64d0612 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 6825a564cf 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 3239aa9b2d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards b5e18b454e 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 1a162f069a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards b0c51965f3 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 0f2606e9cc 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 2a3924d139 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 0c5541025d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 69a36dc6da 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards f02ebb25a4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ef672692dc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 57f2cbb82e 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards eacc83ced8 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 93c464e166 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 9c06cc273b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards d9b422c165 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 18516d9735 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 0d76502271 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards f466d6e006 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 266e629fe6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards d6c23b0aa7 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 5115143683 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards da23bc2047 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f0f0851301 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 772a40ad41 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards e66b5ce669 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 5f8a8970fe 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 96c522d6ea 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 569c8d3254 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 1cf1958f39 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards eb293b5379 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 93b3e266a4 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 05bdbbc428 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 4a2e5361c0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 4b773a8092 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 851ff89be7 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 3d3f74396e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new a26316aa79 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 288b6d135c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new f39ae4dc7f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new e6e8f9b298 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e9ad31dc0c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 963439a1ba 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 0a5c3c8e54 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new e73de71d98 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new affff353cb 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new c621ee101c 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 6356d36542 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 3fa342d3ad 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 8346689f7c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 1fe516c6a8 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e32b95845e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a8c9fd5178 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new c628f9c26a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new dbc29e1341 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 3513f35634 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 4bad54c613 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 17a6ebabb3 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new cd3ed2032f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 1e2a5752ce 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 212dc89ce0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new a2a6fc2b72 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new db2c0e05f0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 3f831eb1e8 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 4bd7a45dfb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new f39fd7f70d 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new b7bcafff00 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new f087c5e3f7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new fdcd4a3a7e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new b3fecf9270 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 202320957e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 45774969f8 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 714740848f 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new b6a51911b2 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 2a74390ef1 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 90deba3f46 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 60c448f29f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4cd5e742db 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 4aff846312 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new bc0d25d6fb 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new ab99909c1b 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 12b13177c4 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new f71e165b2b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 93e8ab15c8 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new b2a24163d9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 630f314d8c 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new ca492ba0d5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new c3004082a4 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 8d7a446869 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new a63064c7bf 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 437011b83c 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 2faaa44fbf 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 02b287c9f6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new dbfe590f42 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new dd8d486b2f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new a943a285e9 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new e20657dcd2 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 298c8808cf 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 8bda57b38c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 79548efe33 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 4876e9906f 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new f82e0cdc8f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new ce36372450 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new b2378efe66 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 37547be9d0 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 650387193d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new bc5c1f364a 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 0aaa0fedde 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 0bb695a876 408: onsuccess: #2662: 1: Success after linux: 11 commits new 537009f9e6 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 62ea8dca17 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new d0cc4e32aa 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new eea91604a0 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new eb3c7dd3b7 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 7c46af8120 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 07a71294e1 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 257d63e616 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new ac75dcfa49 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 5d61249f34 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new e9e1e18955 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 0a7bb11e43 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 2b09a91571 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new e20e32e770 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 63377dc333 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c1a51d3d82 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 86cb2f55d8 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 7c295809d5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 0a5a81c640 427: onsuccess: #7: 1: Success after linux: 26 commits new 7b4b18fdda 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 0001b7f3e9 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 0cdd1fb569 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new d6695f61e2 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 92df184961 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new 30c34ff49e 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 5a79447f9a 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 0a1265dd4e 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 9e2f69d088 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...]
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 (5823b418ce) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 30964 -> 30828 bytes 04-build_abe-stage1/console.log.xz | Bin 71600 -> 71332 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 244492 -> 244632 bytes 08-build_abe-stage2/console.log.xz | Bin 202216 -> 202192 bytes 09-build_abe-gdb/console.log.xz | Bin 38180 -> 38168 bytes 10-build_abe-qemu/console.log.xz | Bin 30820 -> 30964 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3260 -> 3028 bytes 13-check_regression/console.log.xz | Bin 7920 -> 6996 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 81 +++---- 13-check_regression/results.compare | 36 +-- 13-check_regression/results.compare2 | 261 ++++----------------- .../{mail-body.txt => results.regressions} | 82 ++----- 14-update_baseline/console.log | 66 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 83 +++---- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++-- results | 41 ++++ sumfiles/g++.log.xz | Bin 3420016 -> 3414960 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3007512 -> 3013180 bytes sumfiles/gcc.sum | 14 +- sumfiles/gfortran.log.xz | Bin 1041360 -> 1039540 bytes sumfiles/gfortran.sum | 14 +- sumfiles/libatomic.log.xz | Bin 2312 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217584 -> 217520 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438336 -> 436888 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 287 insertions(+), 470 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} (58%)