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 dcf3d14319 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards b459dbe96b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards d128c728ae 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 17374d5557 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 4fe834feba 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 8e1717a0b6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 7b9188cff3 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 978593a07a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 6aaff9d6cc 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 4d5a8212f4 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 65feab1ebe 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 4452ebad36 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 19ae46fd51 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 3e0b43c6ba 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards fe15411ba9 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards cc541e86e3 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards af7d4a3936 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 4f68f21d97 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 9362cee3f4 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards e52df10c25 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 675f748b84 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 23d97c80f5 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 6683115ca3 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 295d75acf0 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards cc88a9c7c4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards d186a83686 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards d73828aeb9 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 487d1ad8a3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 981a7f08a2 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards a527cf6b78 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ae286f9a3e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1146edda6d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards c67b67219e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 0af1472876 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards c2db365eaf 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 31e5e355e6 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards c3aa3e221b 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards e15b70bf9f 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 923d2de2a5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards c81317eeb4 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 8307f54277 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards a41a6b8bae 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 23a2b0cfab 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5eb414b942 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 4db90325f6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards cee4c32aab 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 91a6807ea3 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 73429a79fc 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a551ea3309 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 9fcf1f8f4d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 38219855e2 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards c8fecf0925 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 42212e2e6b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 3559d8fc63 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 395234ca45 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 7779594c46 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 328f7ea3dc 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 730d12d58a 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 592ee54d44 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b77dce2c37 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards b4488e6940 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 5e10e91683 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards f8062161e7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards ec960efa5e 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c7b54f5586 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards b2bc618eeb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ab7581dc26 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards ed54575174 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 5a50b0244c 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 2a22b7a3f8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 9cfaa425f7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 32a319fb0f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards b3cb2177f3 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards d55c15ee8b 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards ddf36d5c56 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 8a15960b9e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards b9a72b6843 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards d306e56766 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 9c74b6e35e 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards e53d662b44 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a6040fcfb4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 1a053af4ad 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 1d26257ddd 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards ba6ec2948e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards f80c4f8c0d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ca4750c105 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards f6ae03b661 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 0831adefbd 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards f048a72309 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards b00cfe2681 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 366c33a556 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e2ebaec98b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ec7395454f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards fca9d664c9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 25095eb9e6 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 1907d75190 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards fe27f2b3b2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards ad3f4a3a24 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards b4e6d4d618 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 25bad9d80b 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 1ef18d4cd9 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 67346a2a32 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 0e4c55cc09 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new f9cb4fb389 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 2fb3d83e33 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new e18e2a28b2 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 2e063126b4 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 2d3fd18f7b 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2775714b54 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new ec3849c9ae 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 2d82fb042e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 25366b5b2a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 167f7a1890 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 1423e2eada 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 5b89dc620d 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 2e6ec45619 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b4ade7121d 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 6cc26a55ac 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 8c90c2e2e0 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new ed8abd484f 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 436edcae49 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 969469477b 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 22b327b0d3 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d2f4f91b0d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f9cdb46fc6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new aaa6407840 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 20a713dd7b 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 3acfae11f2 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new f56ded9b34 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new d9ef4c3387 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 6bd8598aaf 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 90d8637426 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 8c10f217ba 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 0efefa4200 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 8fba49a7e0 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new d95d4fcb07 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 4fbafd50b8 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 1f9e7c3ee4 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new ef442a7e18 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new c16148021d 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new a0f3bff082 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 5d5106e3b8 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b5074293df 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 710ba5d881 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4425e26b23 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new b319f17094 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 8255c5ea59 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2d7ec8abec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new a30d621cd0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new a6355b2b8a 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 3bb2afabb2 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 09265c768b 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 85dfe7186d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 4ba04ee382 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 8ce0b627da 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new f311be48c7 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new f6d710097b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a0fc92c739 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new c86df71aed 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 3190f21832 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4649653fe2 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new fb64e68c71 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 044ed1eb22 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 4a86a9ee49 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 20abf006f4 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 33cf38f92f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 3bed398cce 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new a684610a16 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 1852e24d06 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 2223cf17c4 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 363f9a15a0 384: onsuccess: #2205: 1: Success after gcc: 2 commits new b1fdc72bef 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 5984dd3fae 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 472cd87565 387: onsuccess: #2208: 1: Success after gcc: 2 commits new babc48a1e2 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new dd81d39d1f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f01d8d5edd 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new fd2dc6f573 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new d13f464909 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 74cc0588c1 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 546f5d9605 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new b0f2da243c 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 23a0406b6e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new a1058e9abe 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new b6a08f76c6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 26689d8dc8 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 565d3291a9 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new bbdb069afe 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 2b098b6ee8 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new e0c8a2313e 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 5f983d9542 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 4ae54a95a4 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 97e512ed30 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 9480a0e550 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 7e8c98af15 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 6d7b9a4b23 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 62c12bed3d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 6db29434f8 411: onsuccess: #2232: 1: Success after gcc: 3 commits new b678875248 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 8d56d63491 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 547e5fc905 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 5a3e560643 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 754095659d 416: onsuccess: #2237: 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 (dcf3d14319) \ 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 1808 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30904 -> 31244 bytes 04-build_abe-stage1/console.log.xz | Bin 92480 -> 91924 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 237020 -> 236788 bytes 08-build_abe-stage2/console.log.xz | Bin 229520 -> 228580 bytes 09-build_abe-gdb/console.log.xz | Bin 38232 -> 38552 bytes 10-build_abe-qemu/console.log.xz | Bin 32576 -> 32456 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3852 -> 2904 bytes 13-check_regression/console.log.xz | Bin 6140 -> 7256 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 170 ++- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 54 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 26 + sumfiles/g++.log.xz | Bin 2631212 -> 2671256 bytes sumfiles/g++.sum | 52 +- sumfiles/gcc.log.xz | Bin 2187356 -> 2194516 bytes sumfiles/gcc.sum | 2351 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 896088 -> 897864 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216888 -> 217036 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 437640 -> 438900 bytes sumfiles/libstdc++.sum | 33 +- 44 files changed, 1536 insertions(+), 1360 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions