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-arm in repository toolchain/ci/base-artifacts.
discards 57d88e99e1a 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards d38fdd24c59 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e225c4ed023 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 6d073408b87 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3f98a799a91 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 7184d2e2e63 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 8104ffdd63e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7e922a168d9 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 09e737e5b6a 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 034ac082b76 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards bba3b8c2c93 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a226e41f0ac 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 2e57f7e88a2 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards f8848583f26 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards a536d7fc8c6 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards e6b722d9275 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards f326ac6ec54 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards eb2144abb56 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 6b9cff00eba 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 45f9201fe0a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 9e5b21b8a65 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards fae7fb77bca 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 7b7ba48b4f4 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 7830d2b0cf4 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 9fdd843b907 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 7e4ffe5c11c 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 77fbac345cc 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards c63a2529eaf 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 85ecba64baf 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 63c70b016bc 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 2321c527be8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards cfed6c6bac0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards f266e940a9c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 31aa822c070 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards afb477bf88d 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 356a5a40053 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 34de5153110 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 87c1db9e18f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards f3339d7e850 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 245d4e571c9 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 6417e6fb9c2 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 55b5194a1d1 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards c52bdc3a039 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 4aec7d8b51d 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards a7faa03b41c 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 4a80a82a3f8 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards e4c31038924 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 56ce4673898 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards ec4b9b27575 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 28aaa599240 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards dac0b6a5533 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 367231d9ff3 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 3aff64d90bb 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 4e808b26a08 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 1fcbf87980c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 1f4f00ff649 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 50aeb896b04 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 337974fd50d 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 4d4e98e18ed 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards d8a9dada7e3 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 24c64793f84 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards c00b0cf2caf 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards c3a675e07f0 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 780d1a57190 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 34d953607c7 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 3ccdc536696 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards aee2faee926 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 0b7438a359a 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards ca18e0b1363 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards f219ee740fe 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 8d8c7884813 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 31981af7394 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 70de6635375 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 7e5c644d041 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 9b91266969f 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 34a87e0862e 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards d8b4cc14420 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 88d2adf6bf8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 1c66510f729 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 9db60479ec3 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards aff9bc7ed81 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards a9df9ffaa5d 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards fbe3dc6801f 31: onsuccess: #38: 1: Success after linux: 14 commits discards e535efedf52 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 1d48df60325 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards dbe08209cfa 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 02d37f8258f 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 5ca54cdd23d 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards a705e9a1bea 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 7d7470bf026 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards bd77e966176 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards c1adab876a5 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 2d5f0936f6e 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards cbab7133db0 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 7fd6e3949bd 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards 3551408b36e 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 28a9fb84c39 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards 68defedcd9c 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards bc6e58c9d86 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards 02371b97578 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb [...] discards 807797e8a58 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new ea622561f95 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new d3d4bba0b8c 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb [...] new bb6ea388353 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new b821011fd5c 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new c7a685678fb 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 5cf0bbc0479 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new bea6c01bc13 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 781bb253ba6 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 6c96f995d60 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 5047e0411b6 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 87a57a91bf3 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 377b766941b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 2c402b9f8a7 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new b51a94847dd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e8b4a1b90db 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 463faf055f5 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6921b670bf2 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new aa213e2af62 30: onsuccess: #36: 1: Success after binutils: 18 commits new 9424020aaac 31: onsuccess: #38: 1: Success after linux: 14 commits new 1c55869cabe 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 8bea3998f7f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 1a3c900f3c7 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 4e9204f0cee 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 4ae74a0fb20 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 10fa0155428 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new e9a59d560f2 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new b009c2cdede 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new f76bbf66f71 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new a568d29b5c6 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 9949e44c4a3 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new a170310ed2f 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 78b1463dc2b 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 88a1aff8704 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 8b92e8a9100 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 425323e7ec6 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new e95b10425e8 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 5c05930ed8d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 657c9655e50 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 28a253c42fd 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 9517ec7a364 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new afad33fec60 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 7ba99ee20bf 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 0b449dc44e2 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 2f8b683011e 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 2809136ec22 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new dde2fdbbfcd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 2c1cb680dcd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 9048320e2de 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new db7dca8d5bc 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 6090ae71da5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 30b52543f09 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 18529c7bbdd 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new aab4f3ab3cf 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2011ad8198c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new fba1b909158 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new b11adc752b9 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new df159bd3981 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 0a6b744bc4c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 82d69274844 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new c675e52bbb0 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 4f1d9f3e78a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 1a2037b50a2 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 328c38cf95d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 478a5449e3f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new c3299702340 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new a648e081485 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new f68ad959612 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 9c5058bf018 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new e570a3fc296 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 539e7249c7c 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new a183298ec96 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new fcbd8460ba5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 3bf45b56792 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 58d4e2f0616 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 125d4835669 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 0287e1957af 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 37c55f662e5 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 0990abc52af 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new b3569f0b5e9 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 5beba68ad8f 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 11e6c075c3a 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 4139359936d 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new bd4620aee21 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new a430575ba0b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new ec30fd1dad8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 656c1e1b227 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new fea2dde4f9b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new f9a9d1e2ec5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new c3c673ad4b8 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 302bd05e5ae 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new decf05ba5b9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6bf4b12238f 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 4ba735ba7fc 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 942c4efbe77 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 8d1818823fb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new bb587570e06 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new a1d81268d7f 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a2da46ac86a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 46da71851e9 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 68ef978bbf5 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 650ee4f9814 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 21b5278f583 114: onsuccess: #13: 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 (57d88e99e1a) \ 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 1800 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 53440 -> 53688 bytes 04-build_abe-gcc/console.log.xz | Bin 239852 -> 239104 bytes 06-build_abe-linux/console.log.xz | Bin 8260 -> 10116 bytes 07-build_abe-glibc/console.log.xz | Bin 235876 -> 235800 bytes 08-build_abe-gdb/console.log.xz | Bin 50236 -> 51336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 2716 bytes 11-check_regression/console.log.xz | Bin 5900 -> 6064 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 30 ++++++++++++++------------- 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 11928 -> 11920 bytes sumfiles/gdb.sum | 4 ++-- 24 files changed, 48 insertions(+), 46 deletions(-)