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 b3763cd7613 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 44245a7327f 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards fd38f91c023 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f122b0dfac5 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e13d27959e0 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2cdba045d07 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards f33c6d290db 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ddb2bdfb8de 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 7fa8007cd48 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9a4ca8d191b 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 14489559b83 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0678c7c920c 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 0e18882e1e0 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ab59d262697 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards cd90d6b26a3 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 00c8e357df1 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f22abe7640b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards db7792aa779 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 794b3e37359 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 936aa5ba9ed 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards c5d8c26b51d 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards c0be3da3771 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards fd2bb5678e4 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards d1138cea3cc 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 3839428e3cd 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 93dc9b0b60b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards ed4fe90033c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 45ba264f431 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards bc95851d58f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards b03b9bb4c4b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 384fd3accb8 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 0cf999d458c 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 5956ff39ff5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 35908cbb448 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards d60f57a59e2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 99601156e31 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 970b41d7204 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d41160bafb9 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 7b1e896e933 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 3600dd6a21d 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards a371bec5e41 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards c8106e083db 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 2fcef714953 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 521c944cc82 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards d946e6af7ae 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards cf783bc06a8 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards cd19928b717 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards dbe366a3c33 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 8f05b2b3e7d 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 26432ab2a5f 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards d50dbdcac77 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 8348aabad03 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 34c30b07125 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards e4091ea568c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 2bd4220bce9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 0aabcb25e55 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 8a062718e03 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards bb27a3b6f4d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 16ffac5697b 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards c9e538e2cc9 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards fc22f36bc5b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 9d96e669c5c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 727fb0177d1 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 302c911f462 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 6f69cbcf510 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 804a7ef2370 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards c57b08ed20a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 96c48e4410f 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 0d10dc382c5 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 6f6d722fb95 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards d053cb345ce 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 00b3ce735cb 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 79523605132 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 4a019235811 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 8dde4467921 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 2485a779e6e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards cfe37e0ef6e 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards b528237025f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards c076b2f91bd 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 0f97bec59be 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards fd45c64d422 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 9c40a513403 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 9a73a8c51af 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 7f5ecb70fb0 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 80a9039bcff 40: onsuccess: #49: 1: Success after linux: 219 commits discards 65c7b67bf8b 39: onsuccess: #48: 1: Success after glibc: 2 commits discards e31748670a5 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 9665ee46cb3 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards e37cbd4dce4 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 37a14087fe3 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 6959165cbc2 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 0b3f8a7cc49 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards 27beea0bbfb 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards f780272171e 31: onsuccess: #38: 1: Success after linux: 12 commits discards cfc2dac5d8d 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 6844bae7ecd 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0ffad955b20 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 9ef6020e6fd 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b199df0d17b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 6c0aecf4978 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 975dd183501 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 3576182bc14 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 20035e4d236 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new f40224b7fc1 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new b545c04a748 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 047e7420b57 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 762e381895d 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 8af084cb230 30: onsuccess: #36: 1: Success after binutils: 18 commits new 3b945bf2fb6 31: onsuccess: #38: 1: Success after linux: 12 commits new b26ffc0767b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new fdd3255c075 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 58d36ba73b7 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 96991e88f1f 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 97b9b859711 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 08ed0c243cb 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 62ae643793b 38: onsuccess: #46: 1: Success after binutils: 26 commits new 2780f9ae544 39: onsuccess: #48: 1: Success after glibc: 2 commits new 8ab39a12330 40: onsuccess: #49: 1: Success after linux: 219 commits new 5873c19629a 41: onsuccess: #51: 1: Success after binutils: 12 commits new efcd55e3c84 42: onsuccess: #53: 1: Success after linux: 3008 commits new 7a985f64c34 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 7b44b230f12 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new d6f412ac500 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 96bce0bee06 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 2c57a358ce0 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new b5e766bd508 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new c532b3d1a29 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new f9e26078a03 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 32e9593bc3c 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 019e21a74a2 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 590f3de3f27 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 9fbdd4c5f51 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 28ec7af20e2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new fb0ab0c503c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new dabd3cd4ff8 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 0bb907fac1a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new c246af61b2e 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new b54171c4917 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 412c58263b3 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 6d316808b0c 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 9fb28058e1c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 8ab48e851a8 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 8bef8a8db0d 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new ea810e84b34 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 0347e24c7a4 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new bb0686d6bc4 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new aeab4d86de9 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 9ddef169845 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 0ef14d12633 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new e2b4364f100 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 89838c96a22 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new f5afdfc2d1c 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 8e587f47e80 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 8f8856ff929 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 230864dc4bf 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new f1dd598f687 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 8237c90bff4 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 5590f37def7 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 8fc8dbe9b37 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 34663f31002 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new f17e646ce44 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 9b910b081fb 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 1323c1ca5d8 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new b8e2c6250c6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new ecee30e9581 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new b53bcb36af8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new e67ecc11d00 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new fe89a385a60 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new fc41c45d28e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 1f69e707089 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 0c8eb8b0243 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 0efd51a2f26 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 816b618b5dc 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new c4a8185febc 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new de93ce5088f 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 1cb9ba99eb4 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new f698f68b9eb 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 00b5f3c6671 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 232c6eefff8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new e291b0e480c 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new f682ea5d9a5 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new abda25f4427 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new aa816b357e3 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 765aab56ec9 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new bc8fa6b86eb 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ade8255bc67 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f7dfbfd347b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9b129bbe3aa 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 298c9ec3647 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 3debd2c790f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 10b17718a44 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 2b7e61fd485 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f97d260671b 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c717507e5ba 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new be9ef76dd5d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new a0a2423be45 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9d540af3534 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new ba770eb6412 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e7bfad794e1 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 7e7ae118a11 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2d59eca7a82 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e83f3decb4d 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new fd1c21ecc51 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...]
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 (b3763cd7613) \ 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 1756 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 38684 -> 39320 bytes 04-build_abe-gcc/console.log.xz | Bin 204252 -> 205824 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 244928 -> 243916 bytes 08-build_abe-gdb/console.log.xz | Bin 38128 -> 38868 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2380 -> 3172 bytes 11-check_regression/console.log.xz | Bin 5328 -> 6212 bytes 11-check_regression/results.compare2 | 4 ++-- 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 11912 -> 11896 bytes sumfiles/gdb.sum | 4 ++-- 24 files changed, 50 insertions(+), 50 deletions(-)