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-aarch64 in repository toolchain/ci/base-artifacts.
discards 675b88c5da1 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 6f21bb11fb1 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 23787f01c9c 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards d2ef07f71eb 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards e233e559368 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 1d96838b10a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 4f4aa9694ae 127: force: #27: : Failure after baseline build: no new commits discards b77cdbc3f13 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c54ea11bb5d 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards f4b346bc46c 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 1b778ea9b65 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 100114824ed 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 650bfcd258e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7013f5c49cf 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2ca0c38e560 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 368f6a034d5 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a7f6603e0cc 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 77e174ab942 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards daa782fd4fa 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 3ada2b89fd4 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 9413bcb4a15 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 633f737efc7 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d950d924680 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards cd2119076d9 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 0ae52a597d3 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6ecae68b714 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards d1a50839a70 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 57f8c7443fc 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 94eed5c944c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards ece0e5dcefa 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 88444ff3c07 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 927bcdb5b6f 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 714f38b634e 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards a77c207123b 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards f0cd2f1d860 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards e0829460017 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards cd9bc454958 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 165dc41419b 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 377e028928e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards fb240ffa7a2 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards e33a2ecc611 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 9daf54b8b7b 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 422460dbae8 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 34714301ed2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b5b910c3691 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 942030ab9ed 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 03f91c22eb7 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 8400a0a465c 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards a696870aabb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards e52a8213569 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 00bf21b16fe 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 1b0e98d4d10 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 35c0aade175 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 51bfabf8b28 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 83731e8b388 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 19d5846465e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 3b562d4966a 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 428a35b6a68 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 63ba30bfcc8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 7f696c0ae57 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 61a1996ff16 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards a782435972a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards d73079dbd72 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards aefedddc163 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards c3fc1ce10b0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards f01cfb14237 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 953008a9eac 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards f951475447c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards c38801e7bd3 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 735c62e4020 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 103cc9d9277 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 51d59ad8f8e 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 74adf5f5d35 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards d85427ecf6b 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 87567b814e0 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 1b9ff34b346 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 2f861d288d4 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 7564e1e1258 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards fe794f9d233 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards b10e7f74a3a 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards d4f0beb6431 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards b8391e57c28 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards fb939c87a0f 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards fe51c38a81d 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards cb7598cf7e1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 634d48f63c5 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 121bb9be834 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 884aa71f261 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards bb179219f5d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards db5e62fc507 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards ed449dc3d55 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b03945e2e4d 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 89edf88993e 41: onsuccess: #51: 1: Success after binutils: 12 commits discards c4a2de43ca9 40: onsuccess: #49: 1: Success after linux: 219 commits discards 36bdeedce74 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 2b720e5d75a 38: onsuccess: #46: 1: Success after binutils: 26 commits discards a6107c03dfb 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards f626f2b3c1f 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 90453d0789a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards e2ad1121226 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards d3775711081 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 52f6e257146 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new c5ee73a0810 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new d1a2f134558 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 9bd30dfe31a 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new b3329a80947 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1f5f16f8729 38: onsuccess: #46: 1: Success after binutils: 26 commits new 984247b70f9 39: onsuccess: #48: 1: Success after glibc: 2 commits new 07c7865cf6e 40: onsuccess: #49: 1: Success after linux: 219 commits new 45ac9232024 41: onsuccess: #51: 1: Success after binutils: 12 commits new 3bfd5a2e769 42: onsuccess: #53: 1: Success after linux: 3008 commits new c1c8cd0ff91 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 39b0494f331 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new fdb50ed16ef 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 40ce74f976d 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 2165c934cd9 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new cfc8c61d923 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 4e782546ec1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new e363a962a48 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new e5713976064 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new eafcdcd7f07 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new bdd3f390e41 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 3c6484a3e0c 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 56c46810313 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new ec6f4351109 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 5182f5d0638 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 610b11c0b14 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new f1f809a51e6 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 2f513612a89 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 096bd88574d 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new ba9a2216660 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 00a19500e47 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 1c84caa6a37 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 8440114a98b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 35e97ef022a 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 9b57cad4e6a 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 81517a0f879 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new e352d653bcd 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new ef15aaab483 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 32c9dd66227 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 8e6f24a7a8a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new ec8404b37f0 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d5ef13ba535 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 3e5078896a3 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new fcdec097b93 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new cab80db1dce 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new e9a1d21b29e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 5b70d6aa65e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new c6d14a02f11 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 88f6ba24a76 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 234eea0ebdd 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 93b879eacb8 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 3b9b723a2a2 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new fdb6e138b78 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 478bb58c020 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 26e7bec15ef 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 590f67e3f7a 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new af3401b7b28 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new a9f80367233 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new dcf10f270c3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 4f16afde8a4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new fbd63f49f54 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 66e53ba9346 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 0b0a441633e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 816345db71f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 69b35874e26 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new c8bf68f800b 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 77e8531780b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new fef67bbe2a6 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 40e126febac 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 1badd0a7303 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 7c848d22e16 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new d048487701d 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new ef01baa28c4 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 995ab7f9491 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new e6434e5a3c5 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new fcab0145ff4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 4590b9f0618 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ea80f8584be 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 99f0a26f651 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9f0952c1085 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a3bf144f8ea 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 956ab3fb286 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 44234ba5492 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e62461b5837 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 42da9db0f3f 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new db6c0315673 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7a69472410d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b5ddc6ec2d9 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e6a660a0cee 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 78469b62fae 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 1394efc8ae3 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c2d40351c88 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new f99e854b845 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d2013b119af 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 6ff460edd89 127: force: #27: : Failure after baseline build: no new commits new ea54cd411d6 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 52cca8d9c0f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 691d8074386 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new a82982046f9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new 081ea81fa61 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new cd2b878c93b 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 1daf73cc4cd 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...]
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 (675b88c5da1) \ 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 2072 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 34972 -> 35088 bytes 04-build_abe-gcc/console.log.xz | Bin 203808 -> 203064 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 240976 -> 241432 bytes 08-build_abe-gdb/console.log.xz | Bin 34548 -> 34696 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2816 -> 2648 bytes 11-check_regression/console.log.xz | Bin 4696 -> 4308 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14668 -> 14672 bytes sumfiles/gdb.sum | 4 ++-- 24 files changed, 50 insertions(+), 50 deletions(-)