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 056f5a13fb 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards d4029bb72d 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards a120e06852 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards a873b9b0ce 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 6517bd99ea 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 78c9fb6573 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 2e6b4365e7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards a25c4719af 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards eb55425e5f 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 09877f171b 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards d4535b3a1b 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards bcbad0e032 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 63be9e63b6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 56d995ccf8 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards b5157e0f28 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 82d4027f57 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 5e42dfaaf9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 89d255433e 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 65afa38cae 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 9d56316034 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 3456e83d74 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 3661e549a9 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 499e16e85f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 23f6268d3d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards df456bd174 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 0afcbcf17c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards fdc0bb7c62 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards f21426991c 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards e2da2297ba 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 470f99a4b8 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 5b25be6a72 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 3476d0125e 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 2f9332f7f8 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 02906d8a8c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards e2d3a0db45 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards de9171f195 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 76d7bff09e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 181a59a8c5 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 4fe2433fc5 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards f5aa2749de 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards b143ee2cb1 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 278990ae25 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 2f21f34a86 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 86e24cd5eb 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 4f0914697d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards f3b934e3bc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 8eaddf85f9 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards acd1477bda 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 1d7a7aa931 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 995df5a574 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards b10feba84a 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards b4a080873b 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards bdfc9872ce 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards f6e73c05ca 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 82f9434b92 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 4751e83642 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 69f9404910 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 7e4624c539 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 2ba900915d 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards a0c4b1cd53 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 155b5798b4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards fec87f7d6e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 896290132f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards b56f931e75 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 1996f02813 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards a0224d1d01 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards dc083dbe89 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards ffe08a8ad0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 82e787ff86 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards a347659317 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 31e97b6805 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards b1302a9b71 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 3951b5a53a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards a30764d842 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards ec52f082a9 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards f0f24d31d8 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0903d4a33a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4be654b87e 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards e959d1f5b4 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards eec7bb47d1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards d4e91f31b7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 835130a2cf 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards d7f43fdf08 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 25a7042260 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 84db30bfe2 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a3c1a2a647 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 83c7391f2b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards cfc2fbff99 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 216fd0f4fb 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c3e5ba2877 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 272ae35423 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards d1e8ff7fe1 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 05de8c03b1 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards aa0f9666b0 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards ee3d09cc56 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards aac78a15c3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards ce758c04c9 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 28a343891d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b2b9ee9b3d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards c7dd70ae48 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 4676461b58 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 73101d9880 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new bcda4eff58 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 05ca66035e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 4155890331 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 61045d1408 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 4ca79ae9d9 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 29b8145c12 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new e259b11e19 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new ab54bd0693 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 12c3ff6776 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d3889c6f9f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new b9bae5ff89 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 422dd9136e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 336d828a22 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 117f44b23b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 9369b32901 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 48e7340f8c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 14808933ff 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new f2cabd10fa 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new b4a0e63d0b 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 635f19c708 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new c787ce8d39 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 7e980e602e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new d91f72c1d0 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 5c99d25d70 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 01fab438d7 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new a543e57ea7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 5be04eea02 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new dd53335c00 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new faa6741716 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 5ef0b25edd 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 25aff772c1 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 60f80a9e6c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 6177ba492e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new efcf4be7a1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 0f0c779221 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 58f8b44a11 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new bb8cc7bbf3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new aacbc5cb3f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 1fb14b59dd 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 6f8f6b08b4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new d52e875ec6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ca10d409f8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new eaaf0b3652 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 9b3d051934 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 115e0ba111 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new d5d0480998 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 4d46f2e657 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 7c1d88c4d2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new eeab1cb80d 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 2c22216dbd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 53d4ad03d6 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 01d2c6c879 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new b7e119759f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 9863243863 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new efc942d71d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new a57ebd8862 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new a18c540b9d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 703580ab65 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 7722585918 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new e3d81a36df 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new b46740e40d 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new ab673588cf 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 5a399f1d08 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new e22320bfbe 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new ade7c3071c 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 864cf7a709 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 24a01aec10 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new c22e6aa431 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 0319201ba3 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 37bf2d53ff 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 5ff838edf9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new d673f989b1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 0a24bbd97f 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new ee24358617 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 753397a51c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 5476623864 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new e5e90d8490 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 88877e3375 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 71a2ca9b49 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 6e50b44bb9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new be313c8554 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 90cd79a4f1 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 03548cd4d1 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new e99d05dd52 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new c7edcd4189 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new a9cebdd0d9 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 5361d1adc5 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 4fb101f929 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 9bf04fcfa1 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 3e6a07ebac 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 12f57db5cd 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new af08bd32dc 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 227ba60f12 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 4dffa8461c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new a467f36c4e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new b493b56157 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 9a4fef72e9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new bc5f7a43c7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 2f0e20af51 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 6d507dbdfb 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 71fc8c5c3b 405: onsuccess: #2659: 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 (056f5a13fb) \ 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 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31044 -> 31036 bytes 04-build_abe-stage1/console.log.xz | Bin 71108 -> 71316 bytes 06-build_abe-linux/console.log.xz | Bin 9040 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 244124 -> 244380 bytes 08-build_abe-stage2/console.log.xz | Bin 202460 -> 203040 bytes 09-build_abe-gdb/console.log.xz | Bin 38848 -> 38804 bytes 10-build_abe-qemu/console.log.xz | Bin 32248 -> 31668 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3832 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3104 -> 3264 bytes 13-check_regression/console.log.xz | Bin 6452 -> 7324 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 19 ------- 13-check_regression/mail-body.txt | 42 +++++++------- 13-check_regression/results.compare | 21 ++++--- 13-check_regression/results.compare2 | 97 ++++++++++++++++++++++---------- 13-check_regression/results.regressions | 39 ------------- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +++++++-------- mail/mail-subject.txt | 2 +- manifest.sh | 42 +++++++------- results | 39 ------------- sumfiles/g++.log.xz | Bin 3390124 -> 3385600 bytes sumfiles/g++.sum | 30 ++++++++-- sumfiles/gcc.log.xz | Bin 3029792 -> 3012396 bytes sumfiles/gcc.sum | 32 +++++------ sumfiles/gfortran.log.xz | Bin 1040904 -> 1040980 bytes sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217620 -> 217652 bytes sumfiles/libgomp.sum | 7 ++- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434552 -> 431284 bytes sumfiles/libstdc++.sum | 60 +++++++------------- 43 files changed, 252 insertions(+), 305 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