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 eb79b03eb9c 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 6094c2c9bb6 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 82d4078127d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e01395aeab9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 8fc0478c01d 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e4265ca6215 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 8b983474151 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 12740fdc677 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards dcdaa814c11 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 342965e05dc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5e941a56f6d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 3ac5823e71f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f599a35f202 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards edfd7a8e32f 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 73a43b35932 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 85eafdd5460 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards c369a9ed79a 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 20cff9667b8 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 1d16b0dbee6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 7cc2436f4fa 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 46e398d14ef 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards d659d479de6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 48622fe3755 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 8984d04ed68 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards c3ec9d680d1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 88d591f8571 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards e396d2dd9cd 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards c9dfcc77ddc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 9bc02c5db95 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards bfd5e0cca64 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards d51bf617eaa 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 33581d0a76e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 4b43f43f92e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards af153cf973e 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 7b070d3ac90 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 94b76fb225f 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards fa486cddfb0 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards c055ecaa6d2 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 6a1723727ae 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards faf528e667b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 0b4848dd98c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 74b442730e2 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 356d25f3c6c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 705d2616c77 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 0ba6c83d372 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards dc82a361837 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 035be1fc8b2 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 91ffebec284 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards ffbad1e7fc0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards fe4c3ff80b9 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 8be3ae3c06d 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 6bcaa40ce1e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 70cf963501e 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 4798bcd480d 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 8b38b7bb76b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 3b44e48e028 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 505613261a8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 6024eebd865 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards eb15038b590 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 112a9d56528 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards e70a5d107a2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 9b214616cd2 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 3b0b11afb24 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards e92e2fd2ec1 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 19b4170cd1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards cc473396ada 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 1d6d3e3d307 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 623b684bb51 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 0560adba9ee 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards d1b39f77933 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards c263e0e9b9d 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 3afa5ef42b9 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 5f8ec10bd62 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards c03c292ebd8 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 9c9a3c0adec 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 187a988d821 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards af5cb952351 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 0186560dedf 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards f00d963936f 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards ab8a3bd3e09 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 617de9ba4db 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 9ea5f69528a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 6ee500af229 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3c2a3421d71 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 4593c5f4741 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 9dd8924a8d5 31: onsuccess: #38: 1: Success after linux: 14 commits discards a421d77d814 30: onsuccess: #36: 1: Success after binutils: 18 commits discards cdfdb412c72 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards e2d41a72a3c 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards f2cace7e069 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards ade765c7057 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e637414db77 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 7f1d6e0b08e 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards bfcdcaf0587 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards b462d3fdb96 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 395b26376fb 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 3626acfa4f2 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 7240d5e45f1 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards 6d19b0d8522 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards a75c1fe6e9f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards 3f3cae9253e 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 78516c61a64 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new ffd6434249f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 816ab4051c4 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 51bc5bbfa8c 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 8903e24926c 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 059da8f4847 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 5025bcbe019 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 35e18a4469e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new a71152e3d58 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 8b6542bd882 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 310ca396c66 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 95613d0e707 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 938b5c682fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new c2e6b17e211 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new cba7309e4ed 30: onsuccess: #36: 1: Success after binutils: 18 commits new 5c94d2b5384 31: onsuccess: #38: 1: Success after linux: 14 commits new 39884a7332b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new c7b51602fd4 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new fe39fb6260a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new dd543005005 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new a842fad81f8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 8b57098c656 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 22f5e751e21 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 77633e87087 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 345a8053074 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new ddfafd94fc1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new f598f2e5f17 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 7ddfdd69b0a 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 0d7f92acba0 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new fe5c38a1b28 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 3388c13a4f7 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 80a5cf230c2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new fd999fc3a51 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new cb06b46ebce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new b847389b1b5 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 8dd1ee14f87 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 36265db5a5e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 5d02c6fd12f 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 2150a699e77 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 0d6c1ededfb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 48d690570d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 7bd0c00cede 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new c38cf1d72c4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new c4d1de2758c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 74e63721ab4 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new d3380f7aa87 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new fc20a9a949e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new fb3ab4bbaca 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 5500282febf 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new ea4b981992f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 6048baf8b5e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 1943a053e7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new f28c6de1079 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 66a3f94ef3e 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 774f1059761 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 6d08d1222d8 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 80d7d038190 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 16104aa3686 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 95b6dd74d1c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new d5e1afdb875 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new a2275e6e0bf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new e6e09b26377 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 1118376323f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 343cde431ad 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 333896d3763 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new bf6823a37d2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 01d1dddadb3 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 7ba3f7c37d4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 6912ff399af 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 0650d8d769d 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d6b6e56605b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 3c23666f0f8 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 49fe39b7706 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 088fb501687 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new eb43971b960 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 91d7f41479b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 38b9760c2aa 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new b59b14df462 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new ac79bc9f4d4 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new f72b33a0f63 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new aa970308e19 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new f7aa9bf1dc5 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new e23daf6bf8e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new ae4a8a90242 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new cc68fdc43c2 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new fb649f316f4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 1cb815d99a7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 1c55bd69508 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6196af1ac07 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 06be110cb5b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 3f35bcc8f81 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 0b849aa77cc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ff7f6a4d2da 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 31d491be9f2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new ac44fd9faa1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 29ff17fb386 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 126490a82e4 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b3da5eabaf8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 435351babe2 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 8efffc9eb63 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 98a1d6ef85d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 5fe18b2a4f9 117: onsuccess: #16: 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 (eb79b03eb9c) \ 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 53872 -> 53404 bytes 04-build_abe-gcc/console.log.xz | Bin 237384 -> 238968 bytes 06-build_abe-linux/console.log.xz | Bin 8632 -> 8772 bytes 07-build_abe-glibc/console.log.xz | Bin 235616 -> 235504 bytes 08-build_abe-gdb/console.log.xz | Bin 51388 -> 51320 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2676 -> 2464 bytes 11-check_regression/console.log.xz | Bin 6216 -> 5748 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 36 +++++++++++++++++----------------- 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 11932 -> 11932 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 46 insertions(+), 46 deletions(-)