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 9e2f69d088 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 0a1265dd4e 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 5a79447f9a 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 30c34ff49e 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 92df184961 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards d6695f61e2 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 0cdd1fb569 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 0001b7f3e9 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 7b4b18fdda 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 0a5a81c640 427: onsuccess: #7: 1: Success after linux: 26 commits discards 7c295809d5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 86cb2f55d8 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards c1a51d3d82 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 63377dc333 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards e20e32e770 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 2b09a91571 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 0a7bb11e43 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards e9e1e18955 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 5d61249f34 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards ac75dcfa49 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards 257d63e616 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 07a71294e1 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 7c46af8120 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards eb3c7dd3b7 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards eea91604a0 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards d0cc4e32aa 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 62ea8dca17 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 537009f9e6 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 0bb695a876 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 0aaa0fedde 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards bc5c1f364a 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 650387193d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 37547be9d0 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards b2378efe66 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards ce36372450 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards f82e0cdc8f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 4876e9906f 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 79548efe33 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 8bda57b38c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 298c8808cf 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards e20657dcd2 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards a943a285e9 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards dd8d486b2f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards dbfe590f42 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 02b287c9f6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 2faaa44fbf 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 437011b83c 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards a63064c7bf 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 8d7a446869 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards c3004082a4 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards ca492ba0d5 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 630f314d8c 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards b2a24163d9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 93e8ab15c8 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards f71e165b2b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 12b13177c4 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards ab99909c1b 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards bc0d25d6fb 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 4aff846312 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 4cd5e742db 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 60c448f29f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 90deba3f46 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 2a74390ef1 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards b6a51911b2 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 714740848f 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 45774969f8 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 202320957e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards b3fecf9270 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards fdcd4a3a7e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards f087c5e3f7 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards b7bcafff00 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards f39fd7f70d 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 4bd7a45dfb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 3f831eb1e8 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards db2c0e05f0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards a2a6fc2b72 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 212dc89ce0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 1e2a5752ce 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards cd3ed2032f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 17a6ebabb3 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4bad54c613 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 3513f35634 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards dbc29e1341 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards c628f9c26a 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a8c9fd5178 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards e32b95845e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 1fe516c6a8 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 8346689f7c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 3fa342d3ad 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 6356d36542 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards c621ee101c 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards affff353cb 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards e73de71d98 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 0a5c3c8e54 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 963439a1ba 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards e9ad31dc0c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards e6e8f9b298 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards f39ae4dc7f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 288b6d135c 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards a26316aa79 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 3d3f74396e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 0fd7f6beff 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new b59fcdf347 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new d357e60c7a 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new b634196d92 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 12a4229719 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 05dcaeb009 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new b26598bfc1 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 7f3f9ba81b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 16663cf546 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 3e11b78588 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 63f02ef96a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new b594e91ad1 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 2b7a3d98b8 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 6dc42fd24d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 13785e94c7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 41a2b3a91a 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 8ac168c5a0 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 04c1acbdca 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b156603f86 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8f1afce858 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 54e8f46879 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 13d295909d 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 622ac4c5ab 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new df7f8a31d4 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 59a95a18f9 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new ed06767429 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 573bb77638 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new a0fd688764 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 6ae342146d 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 070331a344 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 272baf2420 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new a164bcc561 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 8e1aa3b3cf 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new e465f60cb4 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 47fd112961 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new d3b81e1b21 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 7556d794dd 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new dc4d42cfc7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 0fff02ecbf 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 9345282268 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new decfcf0728 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 5d0f2c9846 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 60ce0f322b 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 8297a3d8aa 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 4b12a66e9e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 0919b86a0b 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 41e54bf9be 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 96af6a7ebd 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new c84dd46e01 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 4c5cd63b98 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new a1a3651d41 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 536023c116 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 990a1a80b0 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 6c90520298 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 03fd4a63e6 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 9f2b989c35 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 4882cc6c9f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 751e16d1b8 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new fb90431e91 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new f4d4afdb3b 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 43df7b0294 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 71789d62d4 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 6d8629bd6a 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 00ffd59789 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new a837fe0ab0 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new eb9ec657f4 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 8e852e2077 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 8f1affd88a 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 49f4cd44a3 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 50f8772430 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 56492863c6 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new c42f495137 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 3d3f653852 408: onsuccess: #2662: 1: Success after linux: 11 commits new 596e9a4622 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new e461f4b20e 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 900fb71d85 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new c5da32b8b4 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 2244758981 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new d86aef186e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 18ee8fdb52 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 766443f2b1 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 678831edf6 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new d7b6c3f3ce 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 23367c84eb 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 46a3d522f3 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 182d60718e 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new a27d8b5dfa 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 86cb9083a3 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f2c194315a 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new f936ae44a1 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new fbc25dd32d 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 8b76f9f4c1 427: onsuccess: #7: 1: Success after linux: 26 commits new f6de4ca9d0 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 393521f7dc 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 058c22d7cc 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 88f5576bd9 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 94361b407a 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new 9a7a873dd0 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 4e838ff33a 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 69753a0935 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 4a7efd955c 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new d00e275072 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...]
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 (9e2f69d088) \ 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 1812 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30828 -> 30868 bytes 04-build_abe-stage1/console.log.xz | Bin 71332 -> 71388 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 244632 -> 244720 bytes 08-build_abe-stage2/console.log.xz | Bin 202192 -> 201900 bytes 09-build_abe-gdb/console.log.xz | Bin 38168 -> 38228 bytes 10-build_abe-qemu/console.log.xz | Bin 30964 -> 31228 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3808 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3028 -> 2956 bytes 13-check_regression/console.log.xz | Bin 6996 -> 6928 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 --- 13-check_regression/mail-body.txt | 42 ++++++++++---------- 13-check_regression/results.compare | 34 +++++++--------- 13-check_regression/results.compare2 | 58 +++++++--------------------- 13-check_regression/results.regressions | 41 -------------------- 14-update_baseline/console.log | 66 ++++++++++++++++---------------- 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 | 44 ++++++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++------------ results | 41 -------------------- sumfiles/g++.log.xz | Bin 3414960 -> 3419788 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3013180 -> 3009904 bytes sumfiles/gcc.sum | 6 ++- sumfiles/gfortran.log.xz | Bin 1039540 -> 1037812 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217520 -> 217740 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436888 -> 435492 bytes sumfiles/libstdc++.sum | 8 ++-- 45 files changed, 149 insertions(+), 274 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions