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 53c4aa595a 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 1d68e04c0b 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards cd511c9336 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 92178fdcef 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 8596cca21a 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 55317dd558 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards ec0ffcc564 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 36b4a452e3 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 238052c299 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards faa6cd7841 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 6ce28f2fc3 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 22a2194145 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 74548bead9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 4908de1b9b 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards cbd35434fa 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 5ab51ae012 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards d00b71f30a 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards a1490d5e7c 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 472b46cd12 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards dcb826fc87 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards a291fc4333 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 3b1819abd8 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 42272445f6 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 9b3f828664 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 29281d9662 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 463b724045 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 33bd26494e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 1e3d76ded6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 711b357e09 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards c2fd62df77 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 59b029a595 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards aee243da8e 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards ecfdb561c4 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 89c149c3cc 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards ac54fc9c2e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 93b3addf3e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards e40906f897 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 0c14437201 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards bfbc37a620 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards ab5741ff26 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards e02ffa8847 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards a78a5256dc 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 564551664d 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 295973ed3d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 39caf0494d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 5d5e7598b2 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards c4b37a0c30 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 20b6e02cf3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 4eb0b1c0eb 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards ab85418dfe 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 42cf793412 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 9217ccbe9a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 58886d2bb7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards d62e58aa00 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 442ab9b23b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards b4c94c8483 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 7ab0010bed 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 4a59e1974c 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards caa8f947da 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards f85584158c 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 84347b8516 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 2900c07578 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards a0641cc7bf 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 6ebb1ce61a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8e0a1623f0 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 64c4773692 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 30256ba474 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards bceef196e8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 5e9e81ab1c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a21f2f1adb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 23dd0b73ea 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 81214095ff 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards fb4cf60331 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 6d75a065f8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards aff847cfc9 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards ebc22e4d8e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards f6880607af 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards fa954d619f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards eb465e5806 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 56b7a3e830 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 29f4354356 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 804b105018 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards a112bbb71d 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 5a2d719d86 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards e9259f9835 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 1770a8c2e9 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 28c4d5f85d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 6cf02bd0f8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards e3183d4a08 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards b9089892fb 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards d3de09e1ee 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3f5abf2f59 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards ac0109f05f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 93388fbaf5 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards d49262508c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 89f90ef898 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 5d3bc64734 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0ea944a8a5 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 5dd95c04df 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 6fc02514ad 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 09e578b922 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 80fc95976c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new df4ab7e384 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5cb5e46cc3 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0b046ddc33 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new c8525045bb 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 18cd65edf0 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 39ae9fa4e4 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 122ebb585a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 1e4e4eca2c 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new f2e8c7d610 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 04edb772aa 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new eb3eb265c3 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 66aaac950c 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new d0abfc5e63 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new c1f88be4d0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 2fb71cdc4c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 64b3cd1a4f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 99b1222917 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 2a54dd7636 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 3a0f045203 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 310e6e32d8 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 1df66fd5ed 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new e9a602db99 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new b228f16419 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new ab1f8a04e0 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 7424b77a60 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a9e520c360 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 05cabfee59 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 2ad7978abf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new ce50b3a29c 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 0cfd4aeac4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 935a26b8df 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 1f0116f257 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 627b85fbcd 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 69711ffee7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new ae01d3d350 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new a20a8b582a 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 5ca761dbb8 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4b0b6b81fd 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 209e4b2859 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 3739e2c105 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new f59548cc9e 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 7254d96e73 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new a0be415fdd 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 842101d426 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 8c47b38bee 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 9b3d1972a4 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 03c40a0d5c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 43daca89c9 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 9f26f0f680 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new cb4434f5bc 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 201d75a0a4 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 23284cba86 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 2aa80c6f93 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new b02e488146 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 6ccf13ce9c 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 31967906cc 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 34f657b5a9 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 2890638fcf 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new fbc8edb5c7 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new fde90d1a08 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new de64e92c2f 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new bc2a270e75 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new e64cd4fda6 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 7c00c29335 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 43b0406c89 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 727778e3a6 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new f944303760 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 496c729f92 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new c2a16257c8 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new f0b21bdfc4 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new c4d6a735fb 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new b235d0397e 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 49e7723702 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new f92ee9dc52 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 744a75c010 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new fc6499a62a 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new bd339033f9 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 0a7384f7fe 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 15f41b78a6 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 993357a2b8 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 3722fec1ab 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 3784f6ecbe 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 5ca81e6cf9 408: onsuccess: #2662: 1: Success after linux: 11 commits new 16b24a9d56 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 375eb6dc44 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new ce6ec62852 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 8fab446eb4 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 9c0d8c8e71 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 576d2497ad 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 94e0e113b6 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new cb73d846ea 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 14d9104804 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 5e200a631d 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new bf3190e4b7 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new bd9e4b3c43 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new f5dea1a9d8 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 77dffd64fb 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 1f657ac373 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 14f518f04d 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new bc06ba4290 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 8b6ba70b5e 426: onsuccess: #6: 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 (53c4aa595a) \ 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 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31012 -> 30908 bytes 04-build_abe-stage1/console.log.xz | Bin 71328 -> 71088 bytes 06-build_abe-linux/console.log.xz | Bin 9132 -> 9000 bytes 07-build_abe-glibc/console.log.xz | Bin 243836 -> 243968 bytes 08-build_abe-stage2/console.log.xz | Bin 202752 -> 202480 bytes 09-build_abe-gdb/console.log.xz | Bin 38644 -> 38648 bytes 10-build_abe-qemu/console.log.xz | Bin 31936 -> 31800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2688 -> 2616 bytes 13-check_regression/console.log.xz | Bin 7144 -> 6416 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 +++ 13-check_regression/mail-body.txt | 53 ++++++++++---------- 13-check_regression/results.compare | 20 ++------ 13-check_regression/results.compare2 | 53 +++++++++++--------- .../{mail-body.txt => results.regressions} | 54 ++------------------ 14-update_baseline/console.log | 46 ++++++++--------- 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 | 55 ++++++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++------- results | 27 ++++++++++ sumfiles/g++.log.xz | Bin 3402216 -> 3406684 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3031604 -> 3035460 bytes sumfiles/gcc.sum | 8 +-- sumfiles/gfortran.log.xz | Bin 1041128 -> 1044328 bytes sumfiles/gfortran.sum | 10 ++-- sumfiles/libatomic.log.xz | Bin 2312 -> 2320 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217484 -> 217364 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438180 -> 438796 bytes sumfiles/libstdc++.sum | 6 +-- 43 files changed, 193 insertions(+), 207 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} (55%)