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 f336eddb15 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0d901868ac 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9a0873ff30 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3f84c7d40f 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8cd095f123 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 25c868c9b9 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 393dfb2e94 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a7b65219d9 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6756a1d644 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards ba3bda9292 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards fc37306344 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards f6cc398979 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards c62b2c1846 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 133913b0be 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 84ac5fe55b 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 0d4e81cf84 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards b0f21476f4 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 972cabd856 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 7e8fae4249 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards ef4bc6ac64 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 22c3fc693d 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 6a497ecde1 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 3de55a6da0 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 7689408807 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards afa832811b 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 21a47bac04 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 44d3f40200 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 8629b4a5bf 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 80647d706d 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 7146f76b59 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 587f257fd2 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 8a073f49bf 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 6391fd8551 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards c25003aed3 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards 12dc8bf1f6 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 0be100c9d7 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards 3756a4f4fb 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards b635eff821 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards cdbcf4c0f3 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards e97a381fb2 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9d6e951454 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 88b978df6f 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards c38b63d058 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards f670dc09d9 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 1392649928 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 534f029d20 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 267ae26bba 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards cc07b8426e 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards aa466158d7 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards b21cd4cee0 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0a566c79ce 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 4fa701b6f4 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 5ea806d710 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards e2231a696a 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 0e0112c857 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 65f24a7ec8 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 1edbc3b905 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 386527b3cd 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 5606abd621 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 9531adb885 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards ae9a78076d 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 335417fd39 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 3fb7f242db 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 52d1771260 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 7871fb5147 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 08ea911104 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 400ab03884 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 1726dfb105 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards a977a9622f 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards ac056eff64 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 939e3b2fcd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards ec236c4f96 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 4874869045 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards e4b60d0690 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 9ab443a316 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 34d73f17eb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards ac1bafce62 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 1974c5a14e 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards e34c7e501e 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 6be10092e5 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards bca01da978 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards e2932fb196 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 0c58821a58 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 52002fe848 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards ec3ad1fdba 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 44fcd44c5b 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 500f1c3d04 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 1729d013b3 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 18add9778c 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 4450526183 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards e1b753d580 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards d6cf81ea42 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 5718183c91 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 98badb0273 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 8d513121b2 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 479fe2fac3 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 0806d7a274 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 1fa5746cdc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 3d47b4ed2e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards ae0053a036 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f52474b603 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new e5f97dfc88 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 1e1fbd9dbd 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 9a396dffff 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ee2258cee2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 8b806a708f 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 6b548f335c 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 3b2a374403 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new c79de3ea6d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new a630aa5e19 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new f84640a9f0 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new b4e73e50d6 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 120eff3419 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new e48ce81cff 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new a0b49680a7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new c17b5d424c 411: onsuccess: #2232: 1: Success after gcc: 3 commits new f97e66ea97 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new ef0120b96b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 1b495513ef 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 265647b085 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 4d18e4b759 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 9783969f27 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 55f2ee293b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new cf2c7f5807 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 1a12df2956 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 3480080bc2 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 77da97c665 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0b94ef9455 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new ba7558884f 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 0e991220c8 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 21f072351b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 928ce204f3 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 5608a70dd3 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 63e631e734 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 96fe53e816 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 3b5a979cbb 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new ef7b717074 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 6aaf8a36e9 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 18b68c240c 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new f6fe29584c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 33715d12ac 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 4e5b3c1e66 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new da7a5785c9 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 52d9e32c3f 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new cdd47b37d8 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 60559c0bec 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new f70e725e73 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 1eaaf402c6 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new af742983bc 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 2c627bfde9 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 203b7dc2f0 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new ce838d1ea7 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7d925d7c97 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new b8271af460 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 8847e684bf 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 8e5f986763 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new b2acf8731f 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new c1644dedd4 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new e4fa68b7be 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 75618a6a0b 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 4070426b46 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 7967e603d8 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new dcaf58e686 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new d9d8f6d640 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 5de488c970 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new b18370063d 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 3440e94942 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new 8b6fa0ee64 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new cd8a127265 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new be85c443c2 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 2f023e267e 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 04dead8d83 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new bdf342edaf 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 65aadc6711 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 93a12b3979 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 79e59d3eb5 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new c969a05c56 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 9d92f25b2a 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new dae5eea150 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 721cc33381 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d60511f2ab 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 1f9c36f2b4 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 700463ff4e 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 92cf93c020 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new a91230e00f 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 1464547519 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 38438a4212 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 3d364bf0d3 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 5ca1d16812 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new f71041132d 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 9098be04bc 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 146f8a73d7 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 25f39afd2d 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 5d06855dcf 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 2f8384e4dd 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ff1e364814 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9489475017 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f76e574e29 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8834c65959 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 74cd8329bc 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 755c755a9b 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 42e839797d 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new de39bd93de 498: onsuccess: #65: 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 (f336eddb15) \ 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 2686252 -> 2686492 bytes 00-sumfiles/gcc.log.xz | Bin 2208416 -> 2210512 bytes 00-sumfiles/gfortran.log.xz | Bin 900600 -> 904528 bytes 00-sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes 00-sumfiles/libgomp.log.xz | Bin 217696 -> 217524 bytes 00-sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes 00-sumfiles/libstdc++.log.xz | Bin 447788 -> 450988 bytes 01-reset_artifacts/console.log.xz | Bin 2228 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 27032 -> 27000 bytes 04-build_abe-stage1/console.log.xz | Bin 89364 -> 89528 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 233848 -> 233544 bytes 08-build_abe-stage2/console.log.xz | Bin 225440 -> 225172 bytes 09-build_abe-gdb/console.log.xz | Bin 34620 -> 34336 bytes 10-build_abe-qemu/console.log.xz | Bin 30972 -> 29284 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7444 -> 7428 bytes 12-build_abe-check_gcc/flaky.xfail | 2 +- 13-check_regression/console.log.xz | Bin 1284 -> 1284 bytes 13-check_regression/results.compare2 | 4 +- 14-update_baseline/console.log | 72 +++++++++++++++++----------------- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 18 ++++----- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- 28 files changed, 53 insertions(+), 53 deletions(-)