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 5d7bbfa920 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 57be3eeaa8 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards c3c10dbbde 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards e35a890d91 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 1bce6a8052 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards e8c897461c 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 8e6c9f9bf5 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 4ee5e9d773 427: onsuccess: #7: 1: Success after linux: 26 commits discards eea1ca6df3 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 3ee4b32eee 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 86971bca6f 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 1bb221b7ec 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 506f99cd72 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 766cc6afc5 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards c93223e6a5 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards e23c3cd29e 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards daf6082481 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 711b8371eb 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards f81d5cc6b1 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards c4362dd710 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 2393fe6c27 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards adc88f40a7 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards d009c6a403 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards 18f379dfd9 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 2043f9768a 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 1019caf2ad 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 08f61102c4 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 1bafbb06c9 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 09644ef43f 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 0fd58bd481 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards c2bf624c84 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 73d11e0665 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 8507077eba 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 6cf409d7f8 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 177c1035c2 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards d1d8e91689 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 2cf9867310 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 1435825273 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards 826f9befc8 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 86d28f44f0 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards c7de87014f 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards f453828eb9 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards b94c1a537d 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 3a8e1d10a1 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards f7772f37da 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards b68baec049 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards dcf3eef113 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 19dc0cfd2d 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 3549238375 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards fbdd1fc833 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards d1ebb992fc 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 81af4d7252 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards acec79564d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 0185c8b1a7 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b6883a7254 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 5f81a2c2c3 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 49edda7431 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards dcf75a60a7 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards a9194b21f3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards efaccc4e98 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards c0b0226e6e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards ebb03b5977 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 7da5670247 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 1d6ae683fa 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 41932a3a2a 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards be928cbe14 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 263d006889 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards edf5a356cb 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 4531c4f367 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards b23db2cffc 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 766c8dbc50 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 32db4f61f6 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 6c6a825295 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 2e46fdc68e 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards acada691a0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards cff7e07475 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 715effb9f3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 0d907e047a 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 54b1364101 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c9428d321f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 211ea82c0a 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 4ac3c5277d 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards f2371e13fb 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards cff4ab7546 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards d864e29953 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 345d170ab6 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 6800f450cb 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ef0c8b0448 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards de8ea943f0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards f686b1de17 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 55cbb326e0 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ce44961ecc 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 7c0027c9c5 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 91e25b1195 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 4044d47cad 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards d22ce32f64 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards c705a4143d 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 553b437bb3 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 1a2a25ded0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 8314c73797 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards fc9073212c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new fd627eebf4 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 4b773a8092 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 4a2e5361c0 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 05bdbbc428 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 93b3e266a4 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new eb293b5379 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 1cf1958f39 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 569c8d3254 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 96c522d6ea 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 5f8a8970fe 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new e66b5ce669 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 772a40ad41 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new f0f0851301 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new da23bc2047 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5115143683 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new d6c23b0aa7 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 266e629fe6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new f466d6e006 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 0d76502271 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 18516d9735 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new d9b422c165 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 9c06cc273b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 93c464e166 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new eacc83ced8 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 57f2cbb82e 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ef672692dc 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new f02ebb25a4 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 69a36dc6da 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 0c5541025d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 2a3924d139 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 0f2606e9cc 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new b0c51965f3 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 1a162f069a 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new b5e18b454e 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3239aa9b2d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 6825a564cf 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 90e64d0612 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new c12de38400 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new e7fea23bf0 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 5ffadb76c7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new b183cc8e89 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new d32d4a0807 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 9309caf2af 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 6913b58c03 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 3d51a93a37 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new 1d88538509 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 7ddb7ef5f9 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 27fcea84db 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 11f06bc0a7 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 98a5472db4 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new c603af3ba7 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 47c02865f2 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 2c12c5562e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 0f9cc4453e 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 08f8ef094a 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 68c5365ed0 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new ce7f5027a5 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 1c1790608e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new fcaf237a7f 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 667479602b 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 0abe177059 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 701ace3396 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new b219977f55 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new c908d544a9 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new d76f826c49 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 921da06efe 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new c7d6796772 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new e5e785543f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new c615c1a4e5 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 29ab0f3202 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new d8b705aa05 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 9deb009851 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new dbb6fc8fce 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 45f81cddd3 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 7210be9514 408: onsuccess: #2662: 1: Success after linux: 11 commits new b2d0ceffb4 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 1b96aed5e4 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 4a3fda70f4 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 29eb71bcc1 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 8f14ba744d 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new b2bb000835 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new ed57f0af87 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new f6f2cdd58a 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 9e2b5747ed 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 69ef0e41c9 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 1195c49cb7 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 516dbafa68 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 3316668603 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new f631a014f3 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 61a6e555d1 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new cbd0fa4aa4 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new d016ed0fc8 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 5909acd44c 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 8df8c36baf 427: onsuccess: #7: 1: Success after linux: 26 commits new cdf42034b4 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 1272f5671f 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new e44fde9b6c 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 50f5bf7759 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 5cf3764c0b 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new d182cb03d2 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 68bbb8b989 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 5823b418ce 435: onsuccess: #15: 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 (5d7bbfa920) \ 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 1828 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32076 -> 30964 bytes 04-build_abe-stage1/console.log.xz | Bin 71972 -> 71600 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 244532 -> 244492 bytes 08-build_abe-stage2/console.log.xz | Bin 202516 -> 202216 bytes 09-build_abe-gdb/console.log.xz | Bin 39460 -> 38180 bytes 10-build_abe-qemu/console.log.xz | Bin 32100 -> 30820 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3812 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3188 -> 3260 bytes 13-check_regression/console.log.xz | Bin 8524 -> 7920 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 14 -- 13-check_regression/mail-body.txt | 83 ++------ 13-check_regression/results.compare | 27 +-- 13-check_regression/results.compare2 | 357 +++++++++++++++++++------------- 13-check_regression/results.regressions | 52 ----- 14-update_baseline/console.log | 66 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 85 ++------ mail/mail-subject.txt | 2 +- manifest.sh | 42 ++-- results | 52 ----- sumfiles/g++.log.xz | Bin 3385344 -> 3420016 bytes sumfiles/g++.sum | 72 ++++++- sumfiles/gcc.log.xz | Bin 3021640 -> 3007512 bytes sumfiles/gcc.sum | 125 +++++++++-- sumfiles/gfortran.log.xz | Bin 1041296 -> 1041360 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217664 -> 217584 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434316 -> 438336 bytes sumfiles/libstdc++.sum | 6 +- 44 files changed, 517 insertions(+), 489 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