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 06d1f02eeed 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 52eb729e488 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards c46d8308460 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards c187474ee0f 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards b2bc213055a 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4ca453df8f1 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c973101d2d9 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 760e332cba8 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 967d2238a76 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ca78f1fcfce 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1dc1a0a1815 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6fe3fbe2549 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b8dbd06cf73 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 12aee22646f 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3e09718fcd8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 63266391843 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards e4eda71abba 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 20c5bb9f18c 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 9f98414b5dd 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 91c133d643c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 9c03b94ed80 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards ed6be2e6b24 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards e5c0f3457df 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 6fb743503ae 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 8b503f80e9d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 1f8a9622efe 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 58fa196dab0 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 8134a11d67e 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 7e617872f88 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 936bfab9f22 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 2a8cbdd784e 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 287b22defa5 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards e86aabddde9 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards f23d7351f05 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 08137571f5d 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 0f75a09bdd6 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 0a9a5d83719 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards d184e5429f9 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 3f952fb8af1 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 68b255a45ed 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 282771b7055 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 77637aa7c11 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 645a8e7ac92 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 6e69a00a36b 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 229ffe8dd3f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards cbb15f18004 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 5f76fd38cc5 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 1f4841f5f0e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 79ac674450d 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 16271e61dc8 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 7227e3499e6 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 639cd1a61d5 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards e50c0f7efad 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 8da9f2514e5 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards c3a3f22b27d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 3511522621b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 8fd8446fc3d 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards c7c22ef4ed9 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 0dbef6cb999 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards ef6edb1cbcf 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 345f09aeddc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 2fbe1596731 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 65261ce7d36 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 8ae7e0dcfa1 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 531aea83041 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 636424e08e2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards f6a7620838b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 39abb9b9e99 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 53e304da154 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 35cf5d1e35a 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards e4899e516c1 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 0a294d84fcb 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 3cd6434beb1 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 75d8006b72d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards b42bfac1176 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards cc8e875c6bb 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 0f04d93161c 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 7e48e06f72c 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards d85f769f313 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 861f96561b4 41: onsuccess: #51: 1: Success after binutils: 12 commits discards d2a7a2b2ea1 40: onsuccess: #49: 1: Success after linux: 219 commits discards 959aa5fd852 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 1538f25515a 38: onsuccess: #46: 1: Success after binutils: 26 commits discards a6ccbb795f7 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards ccadb885557 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 5de86be08f6 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 6828169e63f 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards bad2b9cc928 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards 5fbcaa3cb5a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 10ab6b91d2b 31: onsuccess: #38: 1: Success after linux: 12 commits discards 91937943c5b 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 36213bfe00c 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 901b10b92e7 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards a712cbe8f19 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards fc833075d64 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards b9e5edb28f5 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards f3fcfb8d449 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards b333abb15cc 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 4658562e97e 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ea06820037e 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards fad274bf9a2 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new e65bc89f8b3 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 1be73bca7f8 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 3b6f660e528 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 31d0b0c018f 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 91b1d47c3b5 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 67eeb7d7429 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 18692f56de1 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 95058b9a01f 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new be4dddc52f7 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new efb0d82599b 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c520f7650ec 30: onsuccess: #36: 1: Success after binutils: 18 commits new 430676654db 31: onsuccess: #38: 1: Success after linux: 12 commits new e686da005e0 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 6a5e355fa38 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new e7fe9cb02d5 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 663ca093a13 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 141d64f4fb3 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new d66e8e4ac13 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new de1d1bc4a8b 38: onsuccess: #46: 1: Success after binutils: 26 commits new a0bc33f49ec 39: onsuccess: #48: 1: Success after glibc: 2 commits new 70d9a8832ef 40: onsuccess: #49: 1: Success after linux: 219 commits new 988cef44482 41: onsuccess: #51: 1: Success after binutils: 12 commits new aaf5201fb1d 42: onsuccess: #53: 1: Success after linux: 3008 commits new fe81b044f7b 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 82e3293c1f3 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 63fe18ea3f2 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new fd2ede25633 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 9791504e2be 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 045ce3d8e30 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 598b41789f9 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 6c6ab739ef5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 6b223550718 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new e1281217372 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new f7b70319c05 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 8786fa923bf 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 811cf352bd2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new b5baaea4cb4 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new a53e537c43a 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 2a1eeb59710 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new fe702bccc73 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 1df370ba3f9 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new d594a5b7255 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 20412d97ea6 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new b54ad036c10 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 5c6c5ffa88a 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 0d800d3acee 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 5bd585e518f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new c92d513cd82 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 56c2facd58e 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 8829a8f122a 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 04448b729d2 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 1604c30bee5 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new a26850a0391 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 21c8b468267 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 45e448fede9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 7e37e82dc40 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 474803e0e57 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 53c5b469c04 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 0b105753e3b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new b34db6433b2 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 1fee4258981 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 23d3344acaf 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 1d0caf48d2e 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new ce7c0a25001 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new e939cc97165 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new d0867c40d92 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 0fa7c9d37b2 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new a35b31a3695 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new f289726ea03 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 360f774d66a 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new e92c0b49fd9 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 029c0fbe174 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 324a29c7442 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 04647ce10be 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 1f1a9940408 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new f6f4d48fac7 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 72c4ef56d30 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new e22ae9491a0 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 3de35c035df 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new aec47e66ec5 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new bd0400d3cab 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 15a828ad142 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 6f00ea19f62 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 5d9dfe44b9b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 1ea497acf41 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new d1e1c5f5d23 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 849547bd572 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 4d568058c5f 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new af384785297 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new e84f22114d1 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2bd3b8d9f95 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new df6a0cd0c37 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 26e9b1c67de 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cf2af8de250 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 86584ca43aa 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bcb1acbce64 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c351fd11850 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 974d94c69fb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 6893ada3416 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3f46a91581f 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b333fbbf1bf 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2e9df24127f 121: onsuccess: #15: 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 (06d1f02eeed) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 38964 -> 38764 bytes 04-build_abe-gcc/console.log.xz | Bin 203700 -> 204504 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 9596 bytes 07-build_abe-glibc/console.log.xz | Bin 245848 -> 244480 bytes 08-build_abe-gdb/console.log.xz | Bin 38556 -> 38268 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3752 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2512 -> 2464 bytes 11-check_regression/console.log.xz | Bin 6160 -> 5828 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 62 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++---------- sumfiles/gdb.log.xz | Bin 11904 -> 11916 bytes sumfiles/gdb.sum | 30 ++++++++-------- 25 files changed, 76 insertions(+), 76 deletions(-)