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 71fc8c5c3b 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 6d507dbdfb 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 2f0e20af51 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards bc5f7a43c7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 9a4fef72e9 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards b493b56157 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards a467f36c4e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 4dffa8461c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 227ba60f12 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards af08bd32dc 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 12f57db5cd 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 3e6a07ebac 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 9bf04fcfa1 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 4fb101f929 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 5361d1adc5 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards a9cebdd0d9 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards c7edcd4189 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards e99d05dd52 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 03548cd4d1 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 90cd79a4f1 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards be313c8554 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 6e50b44bb9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 71a2ca9b49 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 88877e3375 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards e5e90d8490 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 5476623864 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 753397a51c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards ee24358617 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 0a24bbd97f 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards d673f989b1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 5ff838edf9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 37bf2d53ff 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 0319201ba3 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards c22e6aa431 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 24a01aec10 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 864cf7a709 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards ade7c3071c 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards e22320bfbe 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 5a399f1d08 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards ab673588cf 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards b46740e40d 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards e3d81a36df 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 7722585918 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 703580ab65 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards a18c540b9d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards a57ebd8862 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards efc942d71d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9863243863 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards b7e119759f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 01d2c6c879 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 53d4ad03d6 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 2c22216dbd 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards eeab1cb80d 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 7c1d88c4d2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 4d46f2e657 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d5d0480998 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 115e0ba111 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 9b3d051934 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards eaaf0b3652 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ca10d409f8 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards d52e875ec6 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 6f8f6b08b4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 1fb14b59dd 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards aacbc5cb3f 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards bb8cc7bbf3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 58f8b44a11 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 0f0c779221 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards efcf4be7a1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6177ba492e 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 60f80a9e6c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 25aff772c1 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 5ef0b25edd 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards faa6741716 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards dd53335c00 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5be04eea02 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a543e57ea7 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 01fab438d7 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 5c99d25d70 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards d91f72c1d0 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 7e980e602e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c787ce8d39 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 635f19c708 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b4a0e63d0b 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards f2cabd10fa 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 14808933ff 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 48e7340f8c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 9369b32901 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 117f44b23b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 336d828a22 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 422dd9136e 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards b9bae5ff89 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards d3889c6f9f 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 12c3ff6776 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ab54bd0693 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards e259b11e19 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 29b8145c12 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 4ca79ae9d9 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 61045d1408 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 4155890331 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 05ca66035e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards bcda4eff58 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 7852e380a5 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 922cde310e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 09f0b9ac33 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 855a52656c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b22ca216ff 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 5854dbeec9 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 18493de311 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new c029b43be3 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 4e408c2620 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 468e8d1a69 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new f9850b9c02 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new fc983cefab 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new e97bfb3d2e 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 683f0dd4c2 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new dea07a9bdb 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5466489666 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 45e375d7f9 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new dfa13a5009 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 1bdb964193 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 71c65dd48d 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9c87ab8743 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 0a8eb8dbdc 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 1ce0447d08 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1180fa2e71 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new e0d10a5a9f 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 195a3f7580 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 42909dcba9 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ce801b33b3 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new f164415561 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 9a1efb80cd 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 8ba406844a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 8d022a125c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new db0b0391ca 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new ca38f5177b 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 1b7ba0c11c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 8086ce6910 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 1d6e8f6c10 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 1ff27ae567 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 18ea395ae1 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new c1a07d8a42 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6a2809e523 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d3d0d9ee02 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 74bf851e12 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new b519f340fc 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new b89ca9d53e 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 5fd64a3cbf 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new e627ff1c09 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 13f20996cd 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 98aa3cf46c 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 484dc7e73e 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 8bcdd9847e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new f26f973281 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 34ef5d6ed4 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 38777c28df 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ef3fe8e9d1 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 70d329e075 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c647db2097 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 4136872478 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new c0645927ec 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 3a344fe85e 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new ac1c095d3f 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 8fe905a48b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 728e9cb904 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3ef9bb9d3e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 9e797ce52e 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 309236cf7a 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new a936acf375 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new a21b3a5bc0 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 9d875b1a3a 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 7486fd5301 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new e76dfc4208 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new f835ed243f 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 236daf39a0 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new ccb60bde61 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 7ac9904c30 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 99fd59c1b7 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 3be73a41ca 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 2cf124b1c4 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new db88fe5c26 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new d58a94de57 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 4815f2d3a8 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 415cc91963 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 7049b2c2f7 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new b3228a8477 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new d9b534d2d4 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 08cfdbca6c 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 09a12d247a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new ed04b6174c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 7cd7604074 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new aada6874ca 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 9197b5f7cc 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 7cfed9a464 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 6fbfedee04 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 15592ebb91 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 567d2d7882 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new bdd86234e3 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new a2ea436c24 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 0d7d5edca6 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 432ef354d3 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 605ef07c01 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new b678cbb69f 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 02fc41557c 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits
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 (71fc8c5c3b) \ 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 1832 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31036 -> 31096 bytes 04-build_abe-stage1/console.log.xz | Bin 71316 -> 71020 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 244380 -> 243752 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 202248 bytes 09-build_abe-gdb/console.log.xz | Bin 38804 -> 39024 bytes 10-build_abe-qemu/console.log.xz | Bin 31668 -> 32136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3820 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3264 -> 2760 bytes 13-check_regression/console.log.xz | Bin 7324 -> 6208 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 14 +++ 13-check_regression/mail-body.txt | 62 +++++++------ 13-check_regression/results.compare | 39 ++++---- 13-check_regression/results.compare2 | 100 +++++---------------- .../{mail-body.txt => results.regressions} | 63 ++++--------- 14-update_baseline/console.log | 64 ++++++------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 64 +++++++------ mail/mail-subject.txt | 2 +- manifest.sh | 28 +++--- results | 49 ++++++++++ sumfiles/g++.log.xz | Bin 3385600 -> 3396028 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3012396 -> 3025332 bytes sumfiles/gcc.sum | 28 +++--- sumfiles/gfortran.log.xz | Bin 1040980 -> 1039920 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217652 -> 217708 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431284 -> 429636 bytes sumfiles/libstdc++.sum | 39 ++++---- 41 files changed, 288 insertions(+), 288 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} (70%)