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 21b5278f583 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 650ee4f9814 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 68ef978bbf5 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 46da71851e9 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a2da46ac86a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a1d81268d7f 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards bb587570e06 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 8d1818823fb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 942c4efbe77 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 4ba735ba7fc 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6bf4b12238f 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards decf05ba5b9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 302bd05e5ae 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards c3c673ad4b8 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards f9a9d1e2ec5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards fea2dde4f9b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 656c1e1b227 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards ec30fd1dad8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards a430575ba0b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards bd4620aee21 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 4139359936d 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 11e6c075c3a 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 5beba68ad8f 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards b3569f0b5e9 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 0990abc52af 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 37c55f662e5 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 0287e1957af 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 125d4835669 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 58d4e2f0616 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 3bf45b56792 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards fcbd8460ba5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards a183298ec96 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 539e7249c7c 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards e570a3fc296 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 9c5058bf018 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards f68ad959612 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards a648e081485 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards c3299702340 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 478a5449e3f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 328c38cf95d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 1a2037b50a2 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 4f1d9f3e78a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards c675e52bbb0 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 82d69274844 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 0a6b744bc4c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards df159bd3981 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards b11adc752b9 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards fba1b909158 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2011ad8198c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards aab4f3ab3cf 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 18529c7bbdd 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 30b52543f09 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 6090ae71da5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards db7dca8d5bc 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 9048320e2de 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 2c1cb680dcd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards dde2fdbbfcd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 2809136ec22 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 2f8b683011e 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 0b449dc44e2 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 7ba99ee20bf 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards afad33fec60 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 9517ec7a364 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 28a253c42fd 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 657c9655e50 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 5c05930ed8d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards e95b10425e8 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 425323e7ec6 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 8b92e8a9100 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 88a1aff8704 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 78b1463dc2b 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards a170310ed2f 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 9949e44c4a3 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards a568d29b5c6 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards f76bbf66f71 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards b009c2cdede 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards e9a59d560f2 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 10fa0155428 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 4ae74a0fb20 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 4e9204f0cee 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 1a3c900f3c7 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 8bea3998f7f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 1c55869cabe 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 9424020aaac 31: onsuccess: #38: 1: Success after linux: 14 commits discards aa213e2af62 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 6921b670bf2 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 463faf055f5 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards e8b4a1b90db 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards b51a94847dd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 2c402b9f8a7 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 377b766941b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 87a57a91bf3 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 5047e0411b6 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 6c96f995d60 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 781bb253ba6 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards bea6c01bc13 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards 5cf0bbc0479 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards c7a685678fb 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards b821011fd5c 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards bb6ea388353 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards d3d4bba0b8c 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb [...] new f8846ffb0f0 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb [...] new b259cea3dc0 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 5946115bfad 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new b06c6e78e95 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new db2befe1e21 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new f23a0f852ce 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 50561595bdd 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 60f14e6b5ce 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new a5034e07e18 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 1dee85b7a84 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 8f0356d1a8b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new f4841d4ac83 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 46ceb4ddaed 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 8c1e4a60b4c 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 460c6717c91 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 120e22a528f 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 1edc35644f1 30: onsuccess: #36: 1: Success after binutils: 18 commits new 58690c11ef7 31: onsuccess: #38: 1: Success after linux: 14 commits new 2e10bcb4445 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new dcbfbf5b5eb 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 79dbeab3fc9 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 03087323b62 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new b4acad57615 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 9c028ac0886 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new e10e172ad6d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 99d0c3f0b5c 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 1cf0bb46505 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 605dc31eec6 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new ddd4fadfb95 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new a6405d02462 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new f1409ccc755 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 8ae16cf80e4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 9816dc6709f 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new b8a494cc14a 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new c2c2f0989ad 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 192918264fd 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 4cf55573aee 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 41e4c0559a7 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 92a41246c09 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 2ea864af6eb 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 8f4d0253350 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 622e6df47c4 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 8b6554ca699 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 1bc3692a344 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 92250d953af 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 91cbb1a9597 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 7f49678b303 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 41be75d37b9 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 5de7ee9d1b2 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 288b78add61 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 097b12d3e2f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new bbaf5b31fcd 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 0e0c19adae8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 6b8142ce48e 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 3753a9f815c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new f1abd830e4a 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 22b8a4b5ad1 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 5c454347291 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 7248eb9aa94 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 59a4bc6d2a8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new d9c05e140f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 3f44f37ea79 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new d22c2345d47 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new cc7ac157eb2 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new f88b0bf5a76 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 6b9fc0a44b4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 328add02f58 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 014d7767777 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new b4f534d04ec 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new f0af92bc5f7 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new b4b13139ec4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 36e79038dcc 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 4fa9561130e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 37912436c55 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 0e126f14668 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 1e104227fb4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new efffbae4bb8 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new baeee415240 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new f39dc09873e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new e170e45cc7f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 7ae1b594e10 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 00dcde20fe3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e8d870b9efd 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 6ed3bbe5668 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new f733c8675d5 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 4878b211b0c 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new d5247de1bc4 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 615d1646c21 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new dc0a36c90d5 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 13f281de65d 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 05d760575c6 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 9a68871d8e3 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a2609c3246b 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 87dda0336f8 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4d05407b23e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 73405f30e23 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 4c637d34f33 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7d5f0f54f5b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b47133f374a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a2b22b87f0b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 0c7b931c766 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new bbfb5e5ffbb 115: onsuccess: #14: 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 (21b5278f583) \ 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 1772 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 53688 -> 53768 bytes 04-build_abe-gcc/console.log.xz | Bin 239104 -> 240636 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 10116 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 235800 -> 235272 bytes 08-build_abe-gdb/console.log.xz | Bin 51336 -> 51308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2716 -> 2568 bytes 11-check_regression/console.log.xz | Bin 6064 -> 6136 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 11920 -> 11924 bytes sumfiles/gdb.sum | 30 +++++++++++++-------------- 26 files changed, 67 insertions(+), 67 deletions(-)