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-arm in repository toolchain/ci/base-artifacts.
discards e50e9c599f 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards dba17df3c3 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 1d91d26ca6 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 93a7a5fda7 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 39502c90fa 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards edeba3ec07 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards a0a0ffdd43 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards eb45925156 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards ce8b4e1a05 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards cb5c6db583 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7986dbee8c 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 039ee24ae4 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 52a5a2a13a 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 846809fabf 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ca34c5ec72 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards e76a52fac6 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 4323b0afad 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards b256b023c3 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 8ac35d7546 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 54310b6e9c 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 6ab5ed2f6c 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards e5b96b8d56 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards e01dfe05d7 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards eabb96945f 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 0db72c2b80 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 8b43197c20 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 8575ae774c 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 921e8ea99e 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 358e24508e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 67ee72f150 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 23f1c379e1 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards f3c95b1eec 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards fc004b9faa 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 8fdee7c62d 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards d50ea861c3 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards afdf81f86a 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 71c7d4826f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 6e30f549fb 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 7f3e3780ed 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 7e38aa4c5b 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards ed497b54dc 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards f48dca1ac5 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 2f26c7221c 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 03d3ff8b8d 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 156f1ba045 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards ef430a8420 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 350088642a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards eb22a70da2 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 923b5478c6 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 7d2e3911b0 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards c00af1c200 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards fbc2f14859 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 11565deb03 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 6fad234c06 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards dc0384399c 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 183af1cd36 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 018e271558 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b4c5239a0a 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 05dd36bd7a 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards b3e7c6699e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards f090622e8a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 15f079241b 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards b20761e958 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards bccd6fb5ef 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 8690c117db 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 6904485f4c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 5e47fef907 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards e7d95e6384 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards b935195920 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards b7eabb232b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b1e1fe8d7c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards a14a0cda31 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 5cbc31442e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 8da7bbce6e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 03f68745fc 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 2be69bd7ac 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 30098c57c3 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 3b7f23b9d6 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e181621ac9 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 7d883a2535 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards b685f97be5 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards e8d9c9116f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards de45d5543e 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4f98b44f00 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 1e809053a8 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 1692fc9b00 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 6009c1523e 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards f1775d3567 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards d49bb557d7 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 5350a15c6c 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 07c324edb9 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards b707f90a08 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 0f0fbdd93f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 840bcae9e5 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards aad8418156 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 662cdd2337 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 69b7f9523a 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 74692a0bd3 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0dac1a02e7 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 6af72788d9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 3559541cd6 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b48bf14ce8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b79ad5aa89 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new fb2c82b148 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 714c663071 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 77969d2c6e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 0baf57c3f9 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new c1cd2a9557 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new fab04af4a7 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new de54741828 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 8d585bb645 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new fadde16782 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 9db1968af5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new c16bde0f9f 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 578e9194c9 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 7456122d6a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 1fe7d5969a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 55273b7d8a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 90265cc49c 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 8da95cfcbb 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 239d5ccf5d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c98ae5536d 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 5484c10c5b 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 9aa5fb5af6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new d4f8eca561 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 8ca0c857ec 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 4b47716315 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 496aec2017 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 365cc6f9bb 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 0285834082 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 951db9c4dc 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 6b30272e5a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new d773495115 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 0fa8e3ee57 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 997c2ee341 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 3f1f6d1b22 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 6896245d05 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 12a6efa706 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new dac1992a0e 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new df044d84a5 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new c703ca270e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new e6e9ca5e04 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 53aa0eff32 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new a55f017929 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 7bd255d416 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 4db3d9ce35 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new eda07debfa 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 7203d13034 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new e1229d4bb6 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new a7f4287b59 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 2bd00c5494 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 384eb76bed 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 7fa796ebe5 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new d085b75137 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new bb4aed51fa 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new c0c694d286 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 2ebcbb28b2 411: onsuccess: #2232: 1: Success after gcc: 3 commits new b7404140fb 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 28a80fc895 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new fd3e0a46a5 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new e51e3c735b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new ae7878bdca 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new c1ac11f3f8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new c97b996177 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 2eab24fcb7 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 8d5adfc781 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 602474d93d 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new d79a5693af 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new fe69aae636 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 1f81cbfcdf 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 7556eea130 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 77385aa9c6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new ee1e01e21d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 21c5a43dc8 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 8dc90a037b 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 22b6bdc094 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new f1da9ee633 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 772dde776d 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new ed0d3d9f45 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new cd87f71078 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new d0ca5bc305 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 2cdaf214b1 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 6d4118e51c 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 33f5a985ec 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 26a128a013 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new d7e3dcb78c 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 6d403832ee 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 58ffaf1eb5 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 7752127b86 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 2fa15dc7a0 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 6ff7b35e38 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 01ae5a4349 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new b7436129ed 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a88e85af0e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new ec91e64802 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 607b61eed8 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 9ec7c7a080 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 26f79c7b87 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 58dd246eb2 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 8457325587 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 16d110b9bc 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 1d14b6eb89 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 4b68c1013f 457: onsuccess: #18: 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 (e50e9c599f) \ 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 1744 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30996 -> 31032 bytes 04-build_abe-stage1/console.log.xz | Bin 89560 -> 90056 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9548 -> 10152 bytes 07-build_abe-glibc/console.log.xz | Bin 235920 -> 236320 bytes 08-build_abe-stage2/console.log.xz | Bin 224444 -> 225684 bytes 09-build_abe-gdb/console.log.xz | Bin 38520 -> 38652 bytes 10-build_abe-qemu/console.log.xz | Bin 32024 -> 32544 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3808 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 3028 bytes 13-check_regression/console.log.xz | Bin 7196 -> 7140 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 ++-- 13-check_regression/results.compare | 31 ++- 13-check_regression/results.compare2 | 116 +++++++---- 13-check_regression/results.regressions | 26 --- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 48 ++--- results | 26 --- sumfiles/g++.log.xz | Bin 2669672 -> 2649116 bytes sumfiles/g++.sum | 153 ++++++++------ sumfiles/gcc.log.xz | Bin 2209020 -> 2230136 bytes sumfiles/gcc.sum | 346 ++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896656 -> 895732 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217076 -> 217188 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 440052 -> 432204 bytes sumfiles/libstdc++.sum | 8 +- 46 files changed, 499 insertions(+), 494 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