This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards c1af9e4b8d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards a880fa6f9a 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 5ec7f3ca75 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards bae20147d7 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 951917ad19 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 1a7c9af26f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards de81069113 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards a688776283 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 7562353ef1 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 2d939365d5 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 879bacd54f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards fa7075dd70 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards cbab30ad6d 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 336cbc49c0 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 6b680bc9fc 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 5e10cd48ef 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards a97a4f2608 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 4f1db19ef5 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 4404ae6b63 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 0f6b9ddf18 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 2d8a80f188 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 22d6349c38 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards def06f473b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards b5bc5282ea 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 4e3ad2fcb0 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 809d468fd4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 94082cd42f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards c65b800db6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 0a1c62615b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 4d8d840017 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards b03e547ef8 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards f304599cdf 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards f33fd05296 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 9b54181786 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 35e9d95f5b 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 7e08e0c7b5 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 90972bdaef 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards d87f594789 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 770276c47a 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 3cb8c7972e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 92e790bba4 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 572efcc1e2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 98ca39818e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 05666a4907 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards df1cc36e10 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards d0bee358bb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards c6ae2fca04 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards a2f7e70cbb 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards d488d9c530 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 8bd35eba63 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 3486f34a20 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 2f82ca66b2 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 2956552567 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 566fd8f21a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards ec530a980a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 76c96147f8 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards 47be9e43c4 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 246bc847f9 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards 8df022a3a6 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 105d8a9c75 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 7389eadf32 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards c1b5c4c3a6 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] discards cea24d2dd0 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] discards 3659c63b3c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] discards c27fe66761 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] discards b7fb5b8d4f 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb: [...] discards ed8939c963 38: onsuccess: #45: 1: Success after binutils/gcc/linux/glib [...] discards 9f70c9eb99 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] discards 70b02b44a5 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] discards f1ad870ec1 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] discards ca8a05cd90 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] discards 1a4f915b25 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb: [...] discards a62404f755 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] discards 34d7ac06c5 31: onsuccess: #38: 1: Success after linux: 14 commits discards bb0271cce3 30: onsuccess: #36: 1: Success after binutils: 18 commits discards c112a19343 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] discards a16405cb59 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] discards ccced99541 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] discards 567f4be0c2 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] discards e4a34a637c 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] discards 4189f61458 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] discards fbf13dfe5e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] discards 1f69008003 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] discards 28c3c54a8b 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] discards e36509d9b5 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] discards 4d86543b7c 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] discards 4c2717c34b 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb: [...] discards a4f1129517 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards 92e2c14e93 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] discards fb751de108 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] discards 2d87d2622d 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] discards a6798f52f8 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] discards a02d66d940 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] discards 6182c90958 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] discards 518eba2d93 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] discards 0f1a5b14e3 9: onsuccess: #13: 1: Success after binutils: 3 commits discards 9b0592230f 8: onsuccess: #10: 1: Success after binutils: 4 commits discards d6c1fca59d 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 3 [...] discards c4e1786c7c 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] discards fd378ab6f4 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] discards d2b619d46b 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] new 1705c1405e 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] new 375862b461 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] new 6ba0392fd8 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] new 1ac19c8aaa 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 3 [...] new 1449976d54 8: onsuccess: #10: 1: Success after binutils: 4 commits new b6b3f72b00 9: onsuccess: #13: 1: Success after binutils: 3 commits new 214efaedd2 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] new 213e915076 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] new 02009bb3ac 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] new fccbcfe213 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] new 3a8d2643ef 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] new ab63bfd1a7 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] new 4edab39ad8 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] new eccf85e5f5 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 78455ceb22 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb: [...] new ae0e091410 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] new 9e2bc99b4a 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] new 0f6e58f6f0 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] new 347cdbca3c 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] new 6915ee921a 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] new 000eead3ea 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] new bdced9e2c7 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] new f6dac2c394 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] new 98d29451ae 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] new 8905f2bd6b 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] new ad264c52b8 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] new c0e28ab672 30: onsuccess: #36: 1: Success after binutils: 18 commits new 6db493eb47 31: onsuccess: #38: 1: Success after linux: 14 commits new 331e406dad 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] new 29f0922dbe 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb: [...] new 0290e20e2a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] new 887164c097 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] new 3533637a83 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] new 1446521262 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] new b54a5ac6d4 38: onsuccess: #45: 1: Success after binutils/gcc/linux/glib [...] new 30fdc5eed5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb: [...] new 2ed8f4f09b 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] new ed2210e4b2 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] new 9b3d2a884e 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new 14fe5ba82a 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new 7aa606098e 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 20f22aca3e 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new 505fe67055 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 625531767d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new 00d335464d 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 9aa1723ba4 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 5b91450f0e 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new a7decac497 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 9d6988ac9c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 02a6112bc9 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 939947e3bd 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 220ba5042c 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new dbed1b18ea 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 6ea804c609 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 8e5f778d08 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 87ce11534d 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 5ce35bec35 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 7ee6f2f7f8 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 4297a4e974 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 4c978ee7cd 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 33866756e5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 780bbdaa70 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 323ab3aa11 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new c033439811 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 7a9a18aca7 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new a697749686 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 746b5297a6 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new a7321f5fc7 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 8c9d96f6cc 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 9c92acc61f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 0cfabecc72 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 70859dacc2 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new c682b4605d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 7dadfc9f6c 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 93b4d1f1aa 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 86a2fb6c71 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 211d4f78cd 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new dacce05478 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new ccc9037927 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new cf3ab567ad 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 7dc6b5b370 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 55a38c5d94 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new ffca435459 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 954ad73b85 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new cb55852890 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 2a2186de08 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new b5f6200b48 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new b791ddd0fc 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 1a1704a625 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new f23930f3a9 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 92b559d844 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 40528732ac 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new b350931d56 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new fa86704d04 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 1b2bdd0038 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new e88e7f950e 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 3a79cfb10d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new eeaca934cd 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 033b3d92af 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 2911b77e01 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new e0e166940b 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 169a6f01ee 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...]
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 (c1af9e4b8d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]
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 1780 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 53896 -> 53392 bytes 04-build_abe-gcc/console.log.xz | Bin 239064 -> 239576 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 10156 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 235388 -> 236764 bytes 08-build_abe-gdb/console.log.xz | Bin 50684 -> 51600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2504 -> 2424 bytes 11-check_regression/console.log.xz | Bin 6184 -> 5796 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 36 ++++++++++++++++---------------- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 11928 -> 11964 bytes sumfiles/gdb.sum | 30 +++++++++++++-------------- 26 files changed, 66 insertions(+), 66 deletions(-)