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 15f305dd16 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards e88986db3e 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b943a2216 427: onsuccess: #7: 1: Success after linux: 26 commits discards fb544776d9 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards b39f48bd4b 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards f97a67ed27 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 7495c41ddf 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards d30a143359 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 97d4167dbd 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 4aaa496ba6 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 460ceeeab0 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards f58d6ec7fd 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 98245b0b00 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards aeda0afb53 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 2bc8054118 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 8d09d3389d 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards 155f975ed6 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 64fad77cc8 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards c3de8b6a1e 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards a183fe76a8 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 57083fa2c9 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 16b63a61f5 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 966c85eeb5 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards a0f6a960d5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 2afe847471 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards ad0d22f4fe 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards d2ec330fea 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards b0028a7f83 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 72c1f2b1c5 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 30f304ceaa 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards c5b42c1741 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards a32458923e 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 4d674f6ef1 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 80e32dbfbe 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards e31efee30a 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards fb9a95b341 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 6c8d8082a7 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 6774d9652a 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 7509f67d74 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 6fd69afc23 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards d56446f810 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 9cbec77b03 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 99facaa03f 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 33d7924fc1 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 22fef3e75a 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 3354d5e066 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards c8b5b5a65c 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 426929867b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards b627cec669 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 23f3d139d6 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 5569661cd7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards b32224c8e2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 4ace5134ad 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards ed5dd661e1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 0d49db71a8 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 21cd395833 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards f43f86b44f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 4056d0fc1c 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 0447b904d5 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 6fe4f8217d 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards e802500e5b 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards df01d299bf 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 6da557fdeb 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 61f60e6076 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 150aa0d05e 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 7ebbdc7cdb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 109a5aaea3 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 2e92b7b3ec 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards ce8966d66b 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards ca881067bc 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards ae60acf975 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9ed516949a 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards f73463815f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 6397db81a6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 6009571fac 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards a0c361ff60 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards fdabbf17c9 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 44f2c888c5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards ffaa129de7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards a161919364 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 5da79c76e9 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 6161e304bc 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 169ad51ff1 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 80cc09d45e 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards d25c453c8a 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards fa1d57244c 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards c27b1f5518 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 4f3e663db2 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 31d3f4e357 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 90bf2a24bf 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards e6c8ba6ef8 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards cbfd1ddfde 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 35bd3a437d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 2384df65a4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 37a497904d 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 354da1e73b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards bea1a40512 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 9faca0281c 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards b8b03e19ee 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards bb502c2604 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 3148fce04a 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 182299b41d 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f748e189bd 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 07ca2f7a9d 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new f70ad60d06 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ba38a65ade 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new edc8524733 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 516691acb0 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 9b5c42ac6f 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 4f4d292fe5 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new bb59094d05 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new ed7209dc2a 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 5c244d9a71 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 3f51f782f7 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 137c648a44 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 8f11b8a92b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 76419089b6 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 4deabebcfa 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ae06723705 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 73c6d2066e 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 4c555df2fa 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 91df815a1d 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 84391743a9 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 7001a95247 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new f9ad1c2fdb 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 2492557645 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 225fd9969c 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 7cb12c3bc4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 6d3254720d 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new f1b6873711 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new bc227610d8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 6f030debf8 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new a7556e3ebe 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new ab67e4b433 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new ac4e984a82 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 37357bdfbe 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 5026ce83eb 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new d8b94afe9c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new d62eff46d7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 194232c010 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 6a7a2f9f58 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 560cf38aa3 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 89a86abba0 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new a46b654c25 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 1bc38f3c72 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new e28b4665a6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 3dbfe51254 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new b4f56bd04c 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new d2b8195dd1 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 34f60c2098 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new e231af0b80 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new f39bda015d 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 5d55d8cbad 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 7437d93a5f 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new baa448b0db 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new acd5c07a69 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 11d32268f5 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new c31280cdeb 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 56d9121f4f 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new c21eed0aa6 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new b206c2403d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 2ebe671bd2 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 9871143170 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 7a69e46d1a 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 49dd2962dc 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 2a8544cee3 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new fd81be5941 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new c4893e288c 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 69be566db8 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 9ef6bd5d7a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 8a39a38bc7 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new a30ba68940 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 79036d2f45 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new ae56c71d4d 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 7cc5c932ce 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 4e15963ebc 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new f57a033a15 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 36b782b125 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 18898d92b5 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 3450e299e8 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 755d0413e1 408: onsuccess: #2662: 1: Success after linux: 11 commits new afb4cf1a53 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 729d4b6d3a 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 4550d44351 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new f9cc61f5dc 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 3df2783037 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 03a610940e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new ebc4ca0345 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 021d86b08c 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new e9216b2334 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 4469bacc89 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 00f2787e38 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 20461454c4 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 0df78818fe 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 36850a6550 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new d98e7e8392 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 270c541b00 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 7e6ee14153 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new b630422ed5 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new c58fa854b1 427: onsuccess: #7: 1: Success after linux: 26 commits new 735596ce2d 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new c5c76da56d 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 8a99856bf4 430: onsuccess: #10: 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 (15f305dd16) \ 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 1768 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30964 -> 31228 bytes 04-build_abe-stage1/console.log.xz | Bin 71244 -> 71640 bytes 06-build_abe-linux/console.log.xz | Bin 9436 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 243440 -> 244024 bytes 08-build_abe-stage2/console.log.xz | Bin 202380 -> 202924 bytes 09-build_abe-gdb/console.log.xz | Bin 38968 -> 38932 bytes 10-build_abe-qemu/console.log.xz | Bin 32296 -> 32100 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3840 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2656 -> 3004 bytes 13-check_regression/console.log.xz | Bin 6860 -> 7724 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 26 ------------- 13-check_regression/mail-body.txt | 42 ++++++++++---------- 13-check_regression/results.compare | 21 ++++++---- 13-check_regression/results.compare2 | 47 +++++++++++------------ 13-check_regression/results.regressions | 46 ---------------------- 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 | 46 ---------------------- sumfiles/g++.log.xz | Bin 3392776 -> 3396188 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3023784 -> 3016460 bytes sumfiles/gcc.sum | 48 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 1043972 -> 1036544 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2312 -> 2316 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217220 -> 217540 bytes sumfiles/libgomp.sum | 7 ++-- sumfiles/libitm.log.xz | Bin 2684 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429240 -> 434620 bytes sumfiles/libstdc++.sum | 6 +-- 45 files changed, 180 insertions(+), 294 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