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 2e9df24127f 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b333fbbf1bf 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3f46a91581f 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6893ada3416 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 974d94c69fb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards c351fd11850 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards bcb1acbce64 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 86584ca43aa 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards cf2af8de250 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 26e9b1c67de 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards df6a0cd0c37 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2bd3b8d9f95 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e84f22114d1 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards af384785297 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 4d568058c5f 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 849547bd572 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards d1e1c5f5d23 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 1ea497acf41 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 5d9dfe44b9b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 6f00ea19f62 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 15a828ad142 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards bd0400d3cab 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards aec47e66ec5 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 3de35c035df 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards e22ae9491a0 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 72c4ef56d30 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards f6f4d48fac7 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 1f1a9940408 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 04647ce10be 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 324a29c7442 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 029c0fbe174 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards e92c0b49fd9 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 360f774d66a 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards f289726ea03 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards a35b31a3695 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 0fa7c9d37b2 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards d0867c40d92 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards e939cc97165 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards ce7c0a25001 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 1d0caf48d2e 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 23d3344acaf 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 1fee4258981 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards b34db6433b2 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 0b105753e3b 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 53c5b469c04 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 474803e0e57 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 7e37e82dc40 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 45e448fede9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 21c8b468267 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards a26850a0391 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 1604c30bee5 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 04448b729d2 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 8829a8f122a 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 56c2facd58e 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards c92d513cd82 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 5bd585e518f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 0d800d3acee 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 5c6c5ffa88a 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards b54ad036c10 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 20412d97ea6 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards d594a5b7255 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 1df370ba3f9 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards fe702bccc73 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 2a1eeb59710 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards a53e537c43a 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards b5baaea4cb4 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 811cf352bd2 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 8786fa923bf 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards f7b70319c05 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards e1281217372 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 6b223550718 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 6c6ab739ef5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 598b41789f9 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 045ce3d8e30 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 9791504e2be 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards fd2ede25633 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 63fe18ea3f2 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 82e3293c1f3 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards fe81b044f7b 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards aaf5201fb1d 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 988cef44482 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 70d9a8832ef 40: onsuccess: #49: 1: Success after linux: 219 commits discards a0bc33f49ec 39: onsuccess: #48: 1: Success after glibc: 2 commits discards de1d1bc4a8b 38: onsuccess: #46: 1: Success after binutils: 26 commits discards d66e8e4ac13 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 141d64f4fb3 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 663ca093a13 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards e7fe9cb02d5 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 6a5e355fa38 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards e686da005e0 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 430676654db 31: onsuccess: #38: 1: Success after linux: 12 commits discards c520f7650ec 30: onsuccess: #36: 1: Success after binutils: 18 commits discards efb0d82599b 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards be4dddc52f7 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 95058b9a01f 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 18692f56de1 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 67eeb7d7429 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 91b1d47c3b5 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 31d0b0c018f 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 3b6f660e528 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 1be73bca7f8 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 6202f6a4754 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 615201adf73 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 657da3424c1 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 8efda3a2726 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new fd652578ef1 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 513696e65ea 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 3d5f5bf62e6 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 3692e2405bc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 1822b11ac06 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c285f9390bf 30: onsuccess: #36: 1: Success after binutils: 18 commits new 1b95094f681 31: onsuccess: #38: 1: Success after linux: 12 commits new 55f1bfa83f2 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 93ba45c729a 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 35885b46cad 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new abd2bce1c31 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new dfe748c0bbb 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 14ac0b52ac9 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 484f07175fe 38: onsuccess: #46: 1: Success after binutils: 26 commits new a7a6d5a9ad7 39: onsuccess: #48: 1: Success after glibc: 2 commits new 4e241541fd8 40: onsuccess: #49: 1: Success after linux: 219 commits new bd79ee73484 41: onsuccess: #51: 1: Success after binutils: 12 commits new cfaa3cc4e0a 42: onsuccess: #53: 1: Success after linux: 3008 commits new 06cbed7cb66 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 6021cb57ecc 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4500e8a372c 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 35a66e61a9c 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new e5e976eed80 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 21181307bf1 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new f50b49c6066 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new a203eb7157d 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 75b41d76dc2 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 8031d74d3b8 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new f4da28161cd 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new e7050c07f85 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new f2365ef7636 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new f50b0141c74 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new ed29ad7b549 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 2f169fe19e3 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 7f6f83e9b17 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 084ccb78eea 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new ccbcea65edb 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 3d09c7811ef 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 7eb2763cde6 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 1edfdb019bc 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new b3972e8db0f 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new d7ef96f841e 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 376b8455bac 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new ff0f39da069 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 4aadf8df812 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 2ac8885d531 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 7cd216ec997 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 40484700e6c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new fcfb46160f3 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 8cb1080352a 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 73b0f45bf1a 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new aba1c78756e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new a00782720ed 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 6765ad5d45d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 2a030eeca6d 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 833e9078ede 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new a8e1ea0c12a 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new bee1da421c8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new f7e3b2ed761 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 00638c006c9 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 1bd1e5fb08f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new b8337be3eb4 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new a2cacb7d4b6 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c490b6f7e85 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 01d920625a0 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 0c165809354 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 00ae04f119e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new dded606830c 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new bbb0b6b0c4e 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 9a00d1c7b6d 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 79e0011f70b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 0b77835f89c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 09e2d09d124 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 9c83b30d863 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new df8c0cd17be 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new e73c8d21ed3 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new c9aac3b59c5 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new cd749a44057 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new ca04d4cb8b6 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new ac58c2739b3 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 958f8ecef12 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 8e2521dddf8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 2aef4451a4a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 40831d17299 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new ee95d3f3b5a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new df3976c29a8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8051c1eeb6c 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 9faa2c9ee0b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new bf42f0b9d7e 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new e3a6c9332ae 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1c916f29126 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 53fdd3792c8 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 450217574ec 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 90baf6abc38 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5378a00f2d5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 09e14a9b46d 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7fff17c1199 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 94e56e60b70 122: onsuccess: #16: 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 (2e9df24127f) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 38764 -> 38796 bytes 04-build_abe-gcc/console.log.xz | Bin 204504 -> 204652 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9596 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 244480 -> 244244 bytes 08-build_abe-gdb/console.log.xz | Bin 38268 -> 38488 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3752 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2464 -> 2492 bytes 11-check_regression/console.log.xz | Bin 5828 -> 6164 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- 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 | 36 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 11916 -> 11916 bytes sumfiles/gdb.sum | 30 +++++++++++------------ 26 files changed, 69 insertions(+), 69 deletions(-)