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 8fe8f161da 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 10c8a13ad1 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards f7beeaf4b8 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 8ac4bada27 408: onsuccess: #2662: 1: Success after linux: 11 commits discards adf49b4b92 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards ccadea8501 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 0150c3814e 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards e854b21ff2 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 5817a1f4cf 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards b8f7407eb1 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 0c07c2f555 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 949e6b5d69 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 59c10d0c61 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 48605ec1c2 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 10608841eb 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards b39289497d 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 370d51036e 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 9cc9d52749 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 2ca5177c00 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards ebc607006c 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 3298c1ab7d 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards a74caf3e20 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards fc78f4b18f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 632e3ed7d7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 14313d8477 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards febe132277 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 14df94ce1b 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 2c8f28cb33 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 0eb4c1ed02 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards f1a303d4e9 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 4caeaf6839 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards d87992751e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards 922e07cac7 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards dc197999af 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 608c453382 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 2e005cd5f8 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards efa2a82f20 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 3b57819258 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 2d95bee238 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 107a4df7cf 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 4e591b3ab2 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 4d4458b07f 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 037fc15385 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards eb22a09bb5 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 6d7692f28d 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 51fa5fff73 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 9686c6ef9a 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 16d95d2039 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8880a03ccd 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards c0c0976be0 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards c48ee111e6 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards e2b667e652 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 12acaeccb7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 061b293641 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards c94d35de9c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards f68c9998d2 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards cd4883ef1f 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 144fb0beef 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 08d25d1e66 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 0c2344ca96 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 07f265dd90 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards a0a357523a 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards ab10529d29 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 596b3a1b4b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 6233ee2d94 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f82fba0e30 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 3e9bfccbc9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 3d5b056afb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ee1d6dc361 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards f942691e19 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards b2f825b1cf 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 2b1fc18bad 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards d3a658c8ae 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards ce5049c529 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards d9ccb0ffb0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 92845a7b93 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 8b3b26bcef 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards ecfbdf8b1c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards ad056b96d2 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards de88c9f452 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 2d4ff8bb1a 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 188b14049a 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 5fc5c4462b 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 5e84bce579 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards bfcb5bc9fc 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 51e3943ad6 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 1ebe2d68b1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 48b710f3c2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards bf7bf541d6 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards aa2326990b 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 1d159693aa 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 97e947cc3b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 2833ceb615 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 7776cf7555 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards d627a56dcf 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards ad328d8e80 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards a304513225 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 8073b86322 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards ccf61bb005 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 4f929a39e7 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 409bd749e7 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 0d93fa079c 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 25f93fa1f0 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f24356cd31 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 1bd637b7a6 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 24af73460f 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 8c27455dbe 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 68632f6b97 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new e239d91518 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new cf276e66ae 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 4e0fbae8f5 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 8de287cc02 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 8074fc70c2 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new e2011df7e2 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 5ff32a09a0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new a7249266b3 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new ee60894e3e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 4c35596a58 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 41b4b892e1 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 571a3e61f5 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 886e3d0e16 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new d7b0460839 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 03f5d06ea0 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 63ad2c3f79 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 4719c0bca8 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new c0f398cc9c 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 736d20bd1e 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new ac532dd77f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 59f8cf07fb 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 13f87d5ec0 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 0eeef60100 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new eb088f1eb3 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 65e6e41a04 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new b943077968 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 21300cad80 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 82ef06744b 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 55e9a7f607 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 52ab28ffec 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5ef2ecdc06 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 2bc8858088 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new c8edea2b32 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 07e21989d0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 04280510a5 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new b9c5d807f0 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 8cee6bbeb1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 9a0ec30bfa 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 72abc47fbb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new d3c78271c3 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 68d2608e0e 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new ee8d70ca94 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new e02aa90fcc 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 6cfbf95396 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 3ac3face3c 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 459c4cd6ce 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 27f57f5821 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 349ab79488 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 32e07bf7a9 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new c689893f9b 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 4c38790af0 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 0167c5aa95 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new ebbd3e6d56 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 1f6bc5532a 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new a7d191d55e 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new e3114ea725 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 172caf9c76 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new d93fa33db0 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new a91e1154d6 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 665d970f27 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 0d3132791a 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c5b438f9e5 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new fbb3e0b89f 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 30171e8127 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 4bb7373ee8 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 16b62b1d03 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new ee374d380c 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new a85a1fc1f1 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 7527795b8e 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 28c5eaa9c5 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new b86770fa22 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new c1f26eb1ec 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 99ca9df7e4 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new d35fd0079b 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new acf23e3b2a 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 3a50fab05e 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new c79fae6535 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new a750d09739 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new 9c25718b71 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 32e16f7a9a 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 936b49f472 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 4ee08d303f 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 3eff21f5dd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new eedbcfe4fd 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 82d91e190c 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new df9f559f3a 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 774a612cbf 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 3c186e7cf4 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 23db05bd37 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 195c553da5 407: onsuccess: #2661: 1: Success after gcc: 7 commits new a4ed1d8c1b 408: onsuccess: #2662: 1: Success after linux: 11 commits new e4689973c7 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new bb7499aa62 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new e417387799 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 3879d3d3f9 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/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 (8fe8f161da) \ 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 1772 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31276 -> 31300 bytes 04-build_abe-stage1/console.log.xz | Bin 70656 -> 70716 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 244724 -> 243900 bytes 08-build_abe-stage2/console.log.xz | Bin 202516 -> 202336 bytes 09-build_abe-gdb/console.log.xz | Bin 38920 -> 38796 bytes 10-build_abe-qemu/console.log.xz | Bin 31504 -> 32076 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3828 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2760 -> 2708 bytes 13-check_regression/console.log.xz | Bin 6368 -> 8004 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 28 ------ 13-check_regression/mail-body.txt | 42 ++++----- 13-check_regression/results.compare | 13 ++- 13-check_regression/results.compare2 | 158 +++++++++++++++++++------------- 13-check_regression/results.regressions | 48 ---------- 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 ++++----- mail/mail-subject.txt | 2 +- manifest.sh | 44 ++++----- results | 48 ---------- sumfiles/g++.log.xz | Bin 3414740 -> 3391756 bytes sumfiles/g++.sum | 18 +++- sumfiles/gcc.log.xz | Bin 3012376 -> 3024232 bytes sumfiles/gcc.sum | 18 +++- sumfiles/gfortran.log.xz | Bin 1036928 -> 1037580 bytes sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217652 -> 217612 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437996 -> 434176 bytes sumfiles/libstdc++.sum | 102 ++++++++++----------- 43 files changed, 292 insertions(+), 360 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