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 fc57b99ed72 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 0d083845883 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards d8f3df0617b 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards b92c1be62be 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 271c997b80f 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 92cbaf7abfd 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0d5bb4459c2 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 47575fe60d6 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2941ea7b8bd 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e272bebff3e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards d689d73ab6d 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 1bf4fcd49ba 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 8e29fe50497 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5bc6761393a 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards faa312a76b3 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 56651d08ff0 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 34c2c369d7b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards fd48896faa2 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards ad874a59ad1 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards dd81b3dc636 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 5568d99d12b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards bdf28478f61 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 9225383d28d 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards e6582a3acb3 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards e0e208fbedd 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards fdc35184893 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards ab48428849d 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 6ecf7fcc4c8 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards e1512e58ffb 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards b2160f29416 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards e3a3a0b0a80 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards aa8ca4c0705 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 6c7549442f0 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards aa690143c0a 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 83a3831b093 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 6d0f1921681 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards ae8a8c444d0 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards a7d6b63d36b 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards b2f12315ef0 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards c40e1d5ab34 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 053f90d610b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 4fb9b799223 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 09de04c3298 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 50ecec0fad9 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards afaaf8d1a3d 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 7a25b67ee85 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 15d554713f7 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards a3a67eee67e 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 1e239d57414 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards af9e7a488aa 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 0a9040eb21c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 6adf9fa8afb 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 8e6b1a0795f 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 7721d5d7210 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards a9d66d51d18 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 83ce52b06f0 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 8d56ce58195 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 0d56d90c603 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 6aceaebb0b1 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 11d7c801817 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards e028ea9c549 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards cbe09cacfdd 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards f53faecf9cc 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 8b33f4c2298 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards d0e9fc67c9d 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 979e2e174ea 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards e319d2deed3 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards e70142757de 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 8a8cd606078 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards b996111cf2e 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 142e075db34 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards e8d7f71e0c2 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 1bcc9ba460f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards c9eae0c613f 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards dc78b1d0e69 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards aca7a3551b5 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 8b8faeef97a 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 25b8fbf89fe 42: onsuccess: #53: 1: Success after linux: 3008 commits discards d9b4eab9570 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 2144020c939 40: onsuccess: #49: 1: Success after linux: 219 commits discards f056079856d 39: onsuccess: #48: 1: Success after glibc: 2 commits discards a9b15078345 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 06f2db0439e 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards f2e8d2017cb 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 14ada56e046 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards eaf3be07f6b 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards d703c3dd26f 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards c706cb917c3 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 1e3336330a0 31: onsuccess: #38: 1: Success after linux: 12 commits discards db06a7de03d 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 2f5fd94e4cb 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards fac1f609234 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 52e5a5acd65 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 7891b716bd7 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 64d23055bd4 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 29cd00a0b18 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 3c36576e1a4 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards aec6ceee850 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 5394b7c7cea 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 85d9066cf1e 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 934f1086400 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 0b37b09b73a 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new fad274bf9a2 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new ea06820037e 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 4658562e97e 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new b333abb15cc 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new f3fcfb8d449 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new b9e5edb28f5 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new fc833075d64 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new a712cbe8f19 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 901b10b92e7 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 36213bfe00c 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 91937943c5b 30: onsuccess: #36: 1: Success after binutils: 18 commits new 10ab6b91d2b 31: onsuccess: #38: 1: Success after linux: 12 commits new 5fbcaa3cb5a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new bad2b9cc928 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 6828169e63f 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 5de86be08f6 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new ccadb885557 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new a6ccbb795f7 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1538f25515a 38: onsuccess: #46: 1: Success after binutils: 26 commits new 959aa5fd852 39: onsuccess: #48: 1: Success after glibc: 2 commits new d2a7a2b2ea1 40: onsuccess: #49: 1: Success after linux: 219 commits new 861f96561b4 41: onsuccess: #51: 1: Success after binutils: 12 commits new d85f769f313 42: onsuccess: #53: 1: Success after linux: 3008 commits new 7e48e06f72c 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 0f04d93161c 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new cc8e875c6bb 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new b42bfac1176 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 75d8006b72d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 3cd6434beb1 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 0a294d84fcb 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new e4899e516c1 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 35cf5d1e35a 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 53e304da154 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 39abb9b9e99 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new f6a7620838b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 636424e08e2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 531aea83041 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 8ae7e0dcfa1 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 65261ce7d36 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 2fbe1596731 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 345f09aeddc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new ef6edb1cbcf 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 0dbef6cb999 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new c7c22ef4ed9 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 8fd8446fc3d 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 3511522621b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new c3a3f22b27d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 8da9f2514e5 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new e50c0f7efad 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 639cd1a61d5 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 7227e3499e6 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 16271e61dc8 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 79ac674450d 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 1f4841f5f0e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 5f76fd38cc5 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new cbb15f18004 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 229ffe8dd3f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 6e69a00a36b 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 645a8e7ac92 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 77637aa7c11 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 282771b7055 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 68b255a45ed 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 3f952fb8af1 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new d184e5429f9 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 0a9a5d83719 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 0f75a09bdd6 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 08137571f5d 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new f23d7351f05 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new e86aabddde9 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 287b22defa5 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 2a8cbdd784e 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 936bfab9f22 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 7e617872f88 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 8134a11d67e 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 58fa196dab0 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 1f8a9622efe 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 8b503f80e9d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 6fb743503ae 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new e5c0f3457df 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new ed6be2e6b24 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 9c03b94ed80 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 91c133d643c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 9f98414b5dd 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 20c5bb9f18c 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new e4eda71abba 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 63266391843 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 3e09718fcd8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 12aee22646f 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new b8dbd06cf73 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 6fe3fbe2549 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1dc1a0a1815 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ca78f1fcfce 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 967d2238a76 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 760e332cba8 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new c973101d2d9 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4ca453df8f1 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b2bc213055a 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new c187474ee0f 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new c46d8308460 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 52eb729e488 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 06d1f02eeed 120: onsuccess: #14: 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 (fc57b99ed72) \ 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 1920 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39320 -> 38964 bytes 04-build_abe-gcc/console.log.xz | Bin 204212 -> 203700 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10216 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 243760 -> 245848 bytes 08-build_abe-gdb/console.log.xz | Bin 38936 -> 38556 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3044 -> 2512 bytes 11-check_regression/console.log.xz | Bin 5824 -> 6160 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 46 ++++++++++++++++++---------------- 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 -> 11904 bytes sumfiles/gdb.sum | 30 +++++++++++----------- 26 files changed, 72 insertions(+), 70 deletions(-)