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 5d793451787 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 46491eb352d 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 018716eaac3 127: force: #27: : Failure after baseline build: no new commits discards 9fa26186a33 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards bccb1c59f6e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e7966d13b8f 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 27bd0693541 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 61eeb1032ad 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards d429974ea64 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 0c0b77ff9c3 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 317c1eef185 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 52234a0c5eb 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ed0023294bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards ad34034d819 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7ef0cf2fcc3 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ea4f077d71b 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4528c0624fe 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 5bfd80fac68 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4441ed25cca 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 089a0cb13fd 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4a82aa07adc 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards eaf5bec77b6 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 901d58d9791 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4616aac39b1 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 5d9dc3f78d6 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 7a8f7648438 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 31049829a50 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 133b3b328ab 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 3f909510b69 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards ff905bf0325 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 14ca63aba96 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 398f49c81e9 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 3551fca7b2c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 26b3aa5060c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards b9dad0cee67 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 544dba220cc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards d30d9488e62 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards cb2335ae92f 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 58e2ee289c8 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 98d46f5f7b0 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 24df5d86e1b 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards e44d2a4e659 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 856bbd19a31 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 8b88998bd17 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 8a076dd8191 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards cd88922cc32 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards af258b37509 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards c7321346c4a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards f41619a8a4b 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards bef349af329 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 70c95762fa0 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 6e9459f5ca5 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards ccc45e76c80 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 19954704c49 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards a097979830d 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards fc7e3efcc87 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 00256ffd294 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 9f0642b4bb9 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 61214d980f3 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 8f11f73608e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 3bf6923e4b2 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 6b85916fe4e 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards dc4a2116703 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 0a35870d12c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards d4faca81703 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards e1f5bab7a1c 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards bbc43260179 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 5b78d212d81 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards f8d987a14c7 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards f77a4b0a2bd 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards b0a173542e5 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 1d85496f1e8 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards dc9cf329df7 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 263d898badb 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 975ee9c0271 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 1a6aad76897 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 3eaf05b2bb2 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 2ff7f33c8ce 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 3a9aa2b28f5 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards bf477443d41 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 64e3a472879 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 544c7737259 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 57f3daf3e85 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 914d8a86e93 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 0da973fd216 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 205d31cc8c8 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards dc9cd95182e 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 862ed77a238 42: onsuccess: #53: 1: Success after linux: 3008 commits discards ed3f5e31c85 41: onsuccess: #51: 1: Success after binutils: 12 commits discards a6fe5b2a5b0 40: onsuccess: #49: 1: Success after linux: 219 commits discards f08f19e98f8 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 3806f616a43 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 87d3cc8d69b 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 27e87b43078 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 25ec0b33ebc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards cdca95bf688 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 0c87cd209f5 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards f70f819450a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 95378671a4b 31: onsuccess: #38: 1: Success after linux: 12 commits discards 7a4cb0c6437 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 58898d3a8ed 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 7d518d65b4e 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c4df462f41a 30: onsuccess: #36: 1: Success after binutils: 18 commits new d87238e9548 31: onsuccess: #38: 1: Success after linux: 12 commits new 6a71ec11858 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 05a352d3cc6 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new a332d6d03b6 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new dda49af7074 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new f194d44462b 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 39c565456d1 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1e1d6bde188 38: onsuccess: #46: 1: Success after binutils: 26 commits new d555adf58ff 39: onsuccess: #48: 1: Success after glibc: 2 commits new 50131aa7ec9 40: onsuccess: #49: 1: Success after linux: 219 commits new aae81d11ae4 41: onsuccess: #51: 1: Success after binutils: 12 commits new 7a3bf34f232 42: onsuccess: #53: 1: Success after linux: 3008 commits new 4d1030d7db0 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new e491b208b59 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 6f17878d0ce 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 56400c8588a 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 5015e0492b7 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 49af75fda0f 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new f68c5a2e62a 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 65327532633 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 6ddc82a5b16 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 991741e951c 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new f3fdde25f09 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new ddcb8ae294f 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new b2099558245 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 096e083fbe1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 68e19c2e278 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new fad58c126e4 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 12333bd3280 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 4b82860d6e8 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 2fbb6ca1cd5 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 49b92559670 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 6e19a9036e0 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 0d24c4565fd 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new ae7323f8025 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 7cc79d621f2 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new ac2e5427b68 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new beb1b2a978b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new d61509b4b98 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 83e129cc6dc 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 04d3741ea16 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 8f7a82760ed 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new bdfcee883ad 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 9f7e189dbac 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new a026aaed5ee 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 2d723ec71ab 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 920a5aff721 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new d8eed63bc40 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 6658d2e785e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 39c1bde3d8f 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new a4915962238 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 5831f92c533 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 4b9ecb9374b 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 6c865c4c599 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new a16b54669c8 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new e61f4c36bd2 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new a4049c3d6c9 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c0aef9ef923 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 548471211a5 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 6068bd4c4b3 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 8b353e74072 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 0325af6b8e0 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new b5d0cb6f024 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new b146933f308 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 1c239486163 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new b58b4467268 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new d02288457e5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new f3e49f1c629 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 0153647f1a6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 4d65d05af41 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 6ff3a37feb4 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 68b3afc1cb4 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 90c35c9780a 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new c24af4d4f45 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 40829d40080 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new de824e4335b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 5405d1b2b1c 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new cf1b2adb7f4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 24c690a8cb5 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2e76441c4f7 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 810c09f44d6 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 31a0eaf47ef 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c3e0246a7c0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new c694be78774 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 481a482ddb6 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 357f91df9e3 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 98c7dc4114f 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 320b1edeb48 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 185d9a9c3f5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 75796b75d17 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 834f5d267a6 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new f52df8c21dc 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d70c38902fa 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new ae02b11ee54 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 915d5d07cd7 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new c98a5b38265 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new d59899688ed 127: force: #27: : Failure after baseline build: no new commits new ce9807bea22 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 40a887ac71a 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new b82882c46b1 130: onsuccess: #33: 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 (5d793451787) \ 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 1780 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 34964 -> 35248 bytes 04-build_abe-gcc/console.log.xz | Bin 204068 -> 203868 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 242292 -> 241872 bytes 08-build_abe-gdb/console.log.xz | Bin 34748 -> 34916 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2752 -> 2916 bytes 11-check_regression/console.log.xz | Bin 5008 -> 4788 bytes 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 31 +++------------- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- 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 | 4 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14608 -> 14636 bytes sumfiles/gdb.sum | 4 +- 26 files changed, 71 insertions(+), 90 deletions(-)