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 3c9bb9ec51 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards ed9a61e01a 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 4eadbeedfa 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 0409ff7629 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards c983af4a63 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 66c2f33327 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 9bcb1a04fb 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards f82edbfc97 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards a51d202e3a 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 51053e2cb9 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards aae5178396 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards ebd60e7feb 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 4e47d8a9cd 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 2e508fe7aa 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 70bcd5069d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c997d23354 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 1c4c6522dc 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 37ec3e26be 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards c7c53d5c73 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards a173fe6c45 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 3323ca2b13 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards fd47e6b146 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards e02737ac93 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 07ba3497c0 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards e477b34f13 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards f1f9c02937 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 0f96986d85 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 70bd8c774c 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 0c6483eff3 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards e0a5955587 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 6b77da1958 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards dae2acc285 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 67e2fe56f5 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 44372aaad2 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 41804d669b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards b8ece8b49e 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ff6c83ae8d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 033d36d97a 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 9643064833 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 9c24e2c77e 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 286a8c903a 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards dd58fd2a7d 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards eeaf8bc841 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 7fcc254ef2 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 6981441ef8 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards ffd52ea617 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards ce455fc154 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 3e3f15d68d 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 16c180ef58 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 5800886824 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 097fb67e19 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 56ab31428c 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 7702c083d0 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 1bc7ae3863 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards fba22c9702 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards 9f1a1d24ca 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards d0b321bd08 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 0c174b7dfb 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] discards 7998ff8207 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards abe50a3fb8 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards 8c55e4872c 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 4b900ce6bb 41: onsuccess: #51: 1: Success after binutils: 12 commits discards c266770308 40: onsuccess: #49: 1: Success after linux: 219 commits discards bdc3f85b32 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 84ff131e07 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 674a02675c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] discards 1cd4a1e222 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] discards ceace9e652 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] discards 82e024f434 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] discards f314f8bb4f 33: onsuccess: #40: 1: Success after binutils/gcc/linux/glib [...] discards 6088171a20 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] discards 74a2e7e228 31: onsuccess: #38: 1: Success after linux: 12 commits discards 7121f8fff8 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 3c5801429f 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] discards 9809c7a7ee 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] discards da5ed9f8bf 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] discards 315184ce60 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] discards 560592c2bb 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] discards 38f71ae6af 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] discards 36f244d9db 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] discards fbd367b7e0 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] discards 02618e3948 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] discards be76c64688 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] discards c7f8579c1a 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] discards af0bb08cf1 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits discards 8425838448 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 commits discards cd4b0b4b8b 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] discards 21f9f533fd 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] discards dde8fad0b9 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] discards db49ed796f 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] discards 60062dc597 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] discards 738b76904f 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] discards ff49985731 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] discards c0f881549c 9: onsuccess: #13: 1: Success after binutils: 3 commits discards c094182136 8: onsuccess: #10: 1: Success after binutils: 5 commits discards 0929bbd1e3 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 2 [...] discards 62de5111b1 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] discards 597bdd6384 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] discards f82f676c5c 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] discards b3902d7dad 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] discards 5e39eccc0c 2: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: 2 [...] new 76cee87058 2: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: 2 [...] new 2ca09b6dff 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] new b0209b47af 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] new e5b1808000 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] new 8d030e17a7 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] new 6dffbb2a8c 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 2 [...] new ada1f667c4 8: onsuccess: #10: 1: Success after binutils: 5 commits new 83ec6ee2df 9: onsuccess: #13: 1: Success after binutils: 3 commits new 5a4bf62b05 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] new 3129960480 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] new 4dd3bd5766 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] new 8ba6d3dfa5 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] new b4c5866099 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] new a7b566ca4c 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] new f0c65a6f8c 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] new 95e460815f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 commits new 9531686f7d 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits new d2bf21c3e0 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] new e638cd66df 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] new 748ba338c7 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] new 437220cf5e 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] new 8e8d120010 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] new e446d10359 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] new 12cf5b1ba2 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] new f0aed4cf3f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] new 6e2e8b6fc5 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] new f8300dcc95 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] new 7eb76deddb 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] new 6c16a778e0 30: onsuccess: #36: 1: Success after binutils: 18 commits new 86f88692df 31: onsuccess: #38: 1: Success after linux: 12 commits new bd1bcff2c4 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] new adb25bd6b0 33: onsuccess: #40: 1: Success after binutils/gcc/linux/glib [...] new 38264475af 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] new 3e6425ed5b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] new 2732cb0893 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] new ae9161791a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] new 93f264d1ea 38: onsuccess: #46: 1: Success after binutils: 26 commits new c762943fdf 39: onsuccess: #48: 1: Success after glibc: 2 commits new a468361d30 40: onsuccess: #49: 1: Success after linux: 219 commits new 90d52a2be4 41: onsuccess: #51: 1: Success after binutils: 12 commits new 874f21c8e5 42: onsuccess: #53: 1: Success after linux: 3008 commits new 04df4292b8 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new 1d458715e0 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 78efefc78a 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new fa82dbd581 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 5173cf1e17 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new ea267485b0 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new 3edf46d8ca 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 5cbd488002 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new e6c5ff8f49 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 16de2163e4 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new f28fd8b0b9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new d2ad1fa165 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 1c9b682596 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new eb79292011 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 6068ca43ed 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 2267ed7d22 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 5fa4c41b28 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new d087cad5e6 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 50298f5c39 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 1276bc71e1 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new d0eeec3a1b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 65dbdb21a2 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new cf46fe8cfe 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 78dc148fae 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 3dd8134d9d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 94d8449f97 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new bd1bdd3910 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new de08478743 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 3d4171af3b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 2b2ac13995 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 45e5c2e97e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new aa8b149e3c 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 007335a0d8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 3acdb5ea74 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 98036c0b71 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 4ff1b6f333 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new aa466d14ea 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new aae594d0e2 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 928472e7af 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 42fc48e697 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 50bf6fc12e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 2a904c5fed 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new a3010fcf21 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new fea038f79d 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new c2edda202f 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new d3f917eb84 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 23e4b6b3b5 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new b20e247c19 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new b2ff26fb37 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new a0656819e8 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 3e33fd5240 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 007c691da7 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 4d24521366 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 8e95056e9a 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 0c5d01513a 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 89d4cfb58a 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 4100467a2b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 36d52b1c97 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 7b74e7e5a4 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new df220d34fe 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new aacffde510 103: onsuccess: #118: 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 (3c9bb9ec51) \ 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 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 38836 -> 38580 bytes 04-build_abe-gcc/console.log.xz | Bin 205472 -> 205628 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 244836 -> 245540 bytes 08-build_abe-gdb/console.log.xz | Bin 39416 -> 39256 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2564 -> 2460 bytes 11-check_regression/console.log.xz | Bin 6268 -> 5408 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 | 32 +++++++++++++-------------- sumfiles/gdb.log.xz | Bin 11940 -> 11932 bytes sumfiles/gdb.sum | 30 ++++++++++++------------- 25 files changed, 64 insertions(+), 64 deletions(-)