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 bbfb5e5ffbb 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0c7b931c766 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a2b22b87f0b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards b47133f374a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7d5f0f54f5b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4c637d34f33 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 73405f30e23 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4d05407b23e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 87dda0336f8 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a2609c3246b 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 9a68871d8e3 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 05d760575c6 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 13f281de65d 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards dc0a36c90d5 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 615d1646c21 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards d5247de1bc4 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 4878b211b0c 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards f733c8675d5 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 6ed3bbe5668 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e8d870b9efd 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 00dcde20fe3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 7ae1b594e10 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards e170e45cc7f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards f39dc09873e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards baeee415240 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards efffbae4bb8 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 1e104227fb4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 0e126f14668 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 37912436c55 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 4fa9561130e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 36e79038dcc 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards b4b13139ec4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards f0af92bc5f7 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards b4f534d04ec 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 014d7767777 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 328add02f58 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 6b9fc0a44b4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards f88b0bf5a76 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards cc7ac157eb2 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards d22c2345d47 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 3f44f37ea79 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards d9c05e140f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 59a4bc6d2a8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 7248eb9aa94 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 5c454347291 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 22b8a4b5ad1 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards f1abd830e4a 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 3753a9f815c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 6b8142ce48e 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 0e0c19adae8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards bbaf5b31fcd 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 097b12d3e2f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 288b78add61 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 5de7ee9d1b2 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 41be75d37b9 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 7f49678b303 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 91cbb1a9597 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 92250d953af 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 1bc3692a344 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 8b6554ca699 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 622e6df47c4 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 8f4d0253350 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 2ea864af6eb 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 92a41246c09 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 41e4c0559a7 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 4cf55573aee 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 192918264fd 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards c2c2f0989ad 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards b8a494cc14a 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 9816dc6709f 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 8ae16cf80e4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards f1409ccc755 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards a6405d02462 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards ddd4fadfb95 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 605dc31eec6 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 1cf0bb46505 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 99d0c3f0b5c 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards e10e172ad6d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 9c028ac0886 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards b4acad57615 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 03087323b62 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 79dbeab3fc9 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards dcbfbf5b5eb 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 2e10bcb4445 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 58690c11ef7 31: onsuccess: #38: 1: Success after linux: 14 commits discards 1edc35644f1 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 120e22a528f 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 460c6717c91 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 8c1e4a60b4c 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 46ceb4ddaed 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f4841d4ac83 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 8f0356d1a8b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 1dee85b7a84 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards a5034e07e18 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 60f14e6b5ce 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 50561595bdd 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards f23a0f852ce 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards db2befe1e21 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards b06c6e78e95 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards 5946115bfad 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards b259cea3dc0 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new c877502c368 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 3f3cae9253e 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new a75c1fe6e9f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 6d19b0d8522 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 7240d5e45f1 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 3626acfa4f2 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 395b26376fb 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new b462d3fdb96 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bfcdcaf0587 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 7f1d6e0b08e 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new e637414db77 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new ade765c7057 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new f2cace7e069 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new e2d41a72a3c 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new cdfdb412c72 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a421d77d814 30: onsuccess: #36: 1: Success after binutils: 18 commits new 9dd8924a8d5 31: onsuccess: #38: 1: Success after linux: 14 commits new 4593c5f4741 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3c2a3421d71 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 6ee500af229 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 9ea5f69528a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 617de9ba4db 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new ab8a3bd3e09 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new f00d963936f 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 0186560dedf 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new af5cb952351 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 187a988d821 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 9c9a3c0adec 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new c03c292ebd8 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 5f8ec10bd62 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 3afa5ef42b9 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new c263e0e9b9d 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new d1b39f77933 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 0560adba9ee 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 623b684bb51 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 1d6d3e3d307 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new cc473396ada 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 19b4170cd1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new e92e2fd2ec1 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3b0b11afb24 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9b214616cd2 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new e70a5d107a2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 112a9d56528 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new eb15038b590 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 6024eebd865 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 505613261a8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3b44e48e028 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 8b38b7bb76b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 4798bcd480d 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 70cf963501e 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 6bcaa40ce1e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 8be3ae3c06d 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new fe4c3ff80b9 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new ffbad1e7fc0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 91ffebec284 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 035be1fc8b2 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new dc82a361837 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 0ba6c83d372 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 705d2616c77 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 356d25f3c6c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 74b442730e2 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 0b4848dd98c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new faf528e667b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 6a1723727ae 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new c055ecaa6d2 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new fa486cddfb0 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 94b76fb225f 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7b070d3ac90 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new af153cf973e 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 4b43f43f92e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 33581d0a76e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d51bf617eaa 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new bfd5e0cca64 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 9bc02c5db95 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new c9dfcc77ddc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new e396d2dd9cd 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 88d591f8571 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c3ec9d680d1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 8984d04ed68 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 48622fe3755 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d659d479de6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 46e398d14ef 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 7cc2436f4fa 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 1d16b0dbee6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 20cff9667b8 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new c369a9ed79a 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 85eafdd5460 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 73a43b35932 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new edfd7a8e32f 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f599a35f202 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3ac5823e71f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5e941a56f6d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 342965e05dc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new dcdaa814c11 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 12740fdc677 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 8b983474151 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e4265ca6215 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8fc0478c01d 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e01395aeab9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 82d4078127d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6094c2c9bb6 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new eb79b03eb9c 116: onsuccess: #15: 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 (bbfb5e5ffbb) \ 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 1752 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 53768 -> 53872 bytes 04-build_abe-gcc/console.log.xz | Bin 240636 -> 237384 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 235272 -> 235616 bytes 08-build_abe-gdb/console.log.xz | Bin 51308 -> 51388 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2568 -> 2676 bytes 11-check_regression/console.log.xz | Bin 6136 -> 6216 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- 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 11924 -> 11932 bytes sumfiles/gdb.sum | 30 +++++++-------- 26 files changed, 81 insertions(+), 81 deletions(-)