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 b3890ff9e5 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c5efe46943 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d6e3911bf0 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 20e2f9aa33 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bf0378dcd6 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e318eeb95d 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d232b1e225 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 76ccaffbe4 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 24a3e269d5 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 2a14179cbd 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards e12d669c49 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards ed01bcfa33 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards e447c43020 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 227c5b265a 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 2c2235077e 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards fe2894f549 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 05f83bf438 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards e672643718 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards bbea763d51 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ea9406365e 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 0934416f92 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 5d2adc8401 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 1859eaac30 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 2eaac676a8 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards b2e6249c24 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 5061117279 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 95cc2aa446 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 8e1d5df66f 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 4c06921f38 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards d7bae1175d 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards cf9fdeb935 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards de8c9c1904 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 8c2253665a 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards c1a47b75ad 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 6c781e7595 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards fc0d8ed5ac 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 0f2e4f9795 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 65a848d46c 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards c54656cd09 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 0b72f81209 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 4511279bda 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 782c7ba096 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 84047c7690 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 67f3963a46 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 4506c7ae4a 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards fc2fd2dbcb 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d19c9fd3f0 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 67358f34fd 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 551235d037 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 5bba7f578c 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 603083b04a 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards b764a8ceb1 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 590586b3c1 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3f74764aca 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 05ffd35718 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 287dc6ff8a 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 7dcd80b6d0 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 8d97ab1124 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 10576d20d8 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards ad3db43b8d 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 2c07bf4e50 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 93b30780e1 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 9243fb23b5 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards cd00dbbacf 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards e0426301b2 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 927021f317 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards b3ed413048 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 1884d4bdc3 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 73ed17606e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards f091e33d8b 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 065887d378 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards e6918b68dc 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 91fb664806 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards d8fd4831e1 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 397a8b4d47 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards dd79650b4c 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards ceb2885409 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 36b0d6acd4 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards eae66d1586 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 8e4b9a9b40 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards d56bfe40b4 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 553f4f985b 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 28eff48732 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 169020ee28 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 5ab066195a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 8a96101298 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards e701209d5c 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 8bde6d8052 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards cbc5d3de33 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 3793dbbdc7 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 4399fbd121 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 9cc5c2ccbe 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 9b54955f7d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 45ce531677 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 04d4285ff3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 4e341645bc 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards ad3dcc97ee 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 8e17410931 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 165e344bf8 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 1d78780eff 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 09623ca051 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new b5f797f2ae 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new f52474b603 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new ae0053a036 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 3d47b4ed2e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 1fa5746cdc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 0806d7a274 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 479fe2fac3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 8d513121b2 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 98badb0273 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 5718183c91 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new d6cf81ea42 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new e1b753d580 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 4450526183 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 18add9778c 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 1729d013b3 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 500f1c3d04 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 44fcd44c5b 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new ec3ad1fdba 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 52002fe848 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 0c58821a58 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new e2932fb196 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new bca01da978 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 6be10092e5 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new e34c7e501e 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 1974c5a14e 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new ac1bafce62 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 34d73f17eb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 9ab443a316 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new e4b60d0690 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 4874869045 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new ec236c4f96 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 939e3b2fcd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new ac056eff64 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new a977a9622f 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 1726dfb105 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 400ab03884 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 08ea911104 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 7871fb5147 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 52d1771260 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 3fb7f242db 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 335417fd39 436: onsuccess: #2260: 1: Success after gcc: 7 commits new ae9a78076d 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 9531adb885 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 5606abd621 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 386527b3cd 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 1edbc3b905 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 65f24a7ec8 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 0e0112c857 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new e2231a696a 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 5ea806d710 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 4fa701b6f4 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 0a566c79ce 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b21cd4cee0 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new aa466158d7 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new cc07b8426e 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 267ae26bba 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 534f029d20 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1392649928 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new f670dc09d9 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new c38b63d058 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 88b978df6f 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 9d6e951454 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new e97a381fb2 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new cdbcf4c0f3 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new b635eff821 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 3756a4f4fb 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 0be100c9d7 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new 12dc8bf1f6 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new c25003aed3 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 6391fd8551 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 8a073f49bf 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 587f257fd2 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 7146f76b59 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 80647d706d 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 8629b4a5bf 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 44d3f40200 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 21a47bac04 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new afa832811b 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 7689408807 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3de55a6da0 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6a497ecde1 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 22c3fc693d 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ef4bc6ac64 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 7e8fae4249 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 972cabd856 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new b0f21476f4 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 0d4e81cf84 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 84ac5fe55b 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 133913b0be 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c62b2c1846 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new f6cc398979 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new fc37306344 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new ba3bda9292 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 6756a1d644 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a7b65219d9 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 393dfb2e94 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 25c868c9b9 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8cd095f123 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3f84c7d40f 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9a0873ff30 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0d901868ac 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f336eddb15 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (b3890ff9e5) \ 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: 00-sumfiles/g++.log.xz | Bin 0 -> 2686252 bytes 00-sumfiles/gcc.log.xz | Bin 0 -> 2208416 bytes 00-sumfiles/gfortran.log.xz | Bin 0 -> 900600 bytes 00-sumfiles/libatomic.log.xz | Bin 0 -> 2284 bytes 00-sumfiles/libgomp.log.xz | Bin 0 -> 217696 bytes 00-sumfiles/libitm.log.xz | Bin 0 -> 2688 bytes 00-sumfiles/libstdc++.log.xz | Bin 0 -> 447788 bytes 01-reset_artifacts/console.log.xz | Bin 2056 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2396 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 27048 -> 27032 bytes 04-build_abe-stage1/console.log.xz | Bin 89284 -> 89364 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 233356 -> 233848 bytes 08-build_abe-stage2/console.log.xz | Bin 225548 -> 225440 bytes 09-build_abe-gdb/console.log.xz | Bin 34384 -> 34620 bytes 10-build_abe-qemu/console.log.xz | Bin 30788 -> 30972 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6672 -> 7444 bytes 12-build_abe-check_gcc/flaky.xfail | 1 + 13-check_regression/console.log.xz | Bin 2324 -> 1284 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/results.compare | 57 +- 13-check_regression/results.compare2 | 39 +- 13-check_regression/results.regressions | 56 - 14-update_baseline/console.log | 68 +- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 57 +- mail/results.regressions | 56 - manifest.sh | 27 +- results | 56 - sumfiles/g++.log.sep.xz | Bin 129940 -> 0 bytes sumfiles/g++.log.xz | Bin 2660784 -> 0 bytes sumfiles/g++.sum.sep | 11016 ------------------------------ sumfiles/gcc.log.sep.xz | Bin 161960 -> 0 bytes sumfiles/gcc.log.xz | Bin 2235456 -> 0 bytes sumfiles/gcc.sum.sep | 5218 -------------- sumfiles/gfortran.log.sep.xz | Bin 53716 -> 0 bytes sumfiles/gfortran.log.xz | Bin 902656 -> 0 bytes sumfiles/gfortran.sum.sep | 2643 ------- sumfiles/libatomic.log.xz | Bin 2276 -> 0 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217588 -> 0 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 0 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 11764 -> 0 bytes sumfiles/libstdc++.log.xz | Bin 445248 -> 0 bytes sumfiles/libstdc++.sum.sep | 313 - sumfiles/xfails.xfail | 646 ++ 51 files changed, 715 insertions(+), 19555 deletions(-) create mode 100644 00-sumfiles/g++.log.xz create mode 100644 00-sumfiles/gcc.log.xz create mode 100644 00-sumfiles/gfortran.log.xz create mode 100644 00-sumfiles/libatomic.log.xz create mode 100644 00-sumfiles/libgomp.log.xz create mode 100644 00-sumfiles/libitm.log.xz create mode 100644 00-sumfiles/libstdc++.log.xz create mode 100644 12-build_abe-check_gcc/flaky.xfail 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 delete mode 100644 mail/results.regressions delete mode 100644 sumfiles/g++.log.sep.xz delete mode 100644 sumfiles/g++.log.xz delete mode 100644 sumfiles/g++.sum.sep delete mode 100644 sumfiles/gcc.log.sep.xz delete mode 100644 sumfiles/gcc.log.xz delete mode 100644 sumfiles/gcc.sum.sep delete mode 100644 sumfiles/gfortran.log.sep.xz delete mode 100644 sumfiles/gfortran.log.xz delete mode 100644 sumfiles/gfortran.sum.sep delete mode 100644 sumfiles/libatomic.log.xz delete mode 100644 sumfiles/libgomp.log.xz delete mode 100644 sumfiles/libitm.log.xz delete mode 100644 sumfiles/libstdc++.log.sep.xz delete mode 100644 sumfiles/libstdc++.log.xz delete mode 100644 sumfiles/libstdc++.sum.sep