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 f41046d2139 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 26f45d31d3b 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards fa42a6632aa 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 564954aa957 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3765ca14394 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 9e4897ecc2b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e22d0f9c0b2 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 3227e39c2c9 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ed2879c8183 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4bcd0e6bbda 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 26024481732 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards d6d0ebd9f2f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards cb2a485c24a 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 537766460b8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e21bd12435b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 04fd09ea74d 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 6d0438d2554 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5d10bfc9503 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 0c467757caa 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards c9030b090f2 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards d1891db2efa 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 454a9e47694 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 0b29316f68c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards d8f85b364e9 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 0d514ca40f9 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 2f3837d3753 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 492bea3fffa 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards e4582ee7b82 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards be0760b177b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 11f5f452b14 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 8ddffd60bee 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 6367729c22d 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 623cb21b56e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 0ae637294af 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 9971b157913 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards a42c1a6c5b1 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 29e4d0d0979 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 04368cc31bc 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 89c2b576ae9 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards b03330ecdae 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 1b0219d82a0 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 637f0356ee3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 2d1e63548a2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards ebdcd88f755 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards cf51b5fdf43 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 804b5d616a9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 24beedaf640 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 943eed8946c 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards df39d276d6c 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 650b9dc81c4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 00316e892a9 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 52510a38112 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 1d9908c248e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards aae4a4c37eb 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards d90146e8ceb 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 4a7d4d31121 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 6f938debb0c 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 3c7d891e945 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards f439b18592a 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 36e529ea443 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 2b8cfb4037f 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards f117a0b73b9 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 9aaad632f35 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 975fecb9876 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards ec30a2b6601 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards a6dfa0bfbc2 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 4ec1741a4f5 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 073dcd9d21c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 686102c4433 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards d7a4424beb4 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 392fb7d7e5e 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 4dc0cc34dbc 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 77e04bf96a7 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 432f77188c5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 15d8f18bfa2 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards ee11370fc37 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 4f01d848f50 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards b8469132ed2 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards f68311757ec 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 6b9c3cf08ff 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards de68859b4a1 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 235fd54623c 42: onsuccess: #53: 1: Success after linux: 3008 commits discards cdb1d17711a 41: onsuccess: #51: 1: Success after binutils: 12 commits discards d2cdfd4057a 40: onsuccess: #49: 1: Success after linux: 219 commits discards e6793263cc4 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 731ffbeadf5 38: onsuccess: #46: 1: Success after binutils: 26 commits discards c44e19c2972 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 2c5c2fe8597 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards fba073275e5 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards a5a883e7b5a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 552198a8768 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards 64091ff268b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 56eea52ba5e 31: onsuccess: #38: 1: Success after linux: 12 commits discards 88a7f3ba5a6 30: onsuccess: #36: 1: Success after binutils: 18 commits discards e7cc87b4664 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards e8cf734841e 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 94fba21e36b 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 7b3dc494749 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards c3748b142c4 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 2345a69744f 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 54854bd5cd0 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new d543cb63ea8 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 975dd183501 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 6c0aecf4978 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new b199df0d17b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 9ef6020e6fd 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 0ffad955b20 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6844bae7ecd 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new cfc2dac5d8d 30: onsuccess: #36: 1: Success after binutils: 18 commits new f780272171e 31: onsuccess: #38: 1: Success after linux: 12 commits new 27beea0bbfb 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 0b3f8a7cc49 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 6959165cbc2 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 37a14087fe3 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new e37cbd4dce4 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 9665ee46cb3 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new e31748670a5 38: onsuccess: #46: 1: Success after binutils: 26 commits new 65c7b67bf8b 39: onsuccess: #48: 1: Success after glibc: 2 commits new 80a9039bcff 40: onsuccess: #49: 1: Success after linux: 219 commits new 7f5ecb70fb0 41: onsuccess: #51: 1: Success after binutils: 12 commits new 9a73a8c51af 42: onsuccess: #53: 1: Success after linux: 3008 commits new 9c40a513403 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new fd45c64d422 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 0f97bec59be 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new c076b2f91bd 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new b528237025f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new cfe37e0ef6e 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 2485a779e6e 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 8dde4467921 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 4a019235811 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 79523605132 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 00b3ce735cb 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new d053cb345ce 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 6f6d722fb95 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 0d10dc382c5 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 96c48e4410f 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new c57b08ed20a 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 804a7ef2370 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 6f69cbcf510 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 302c911f462 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 727fb0177d1 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 9d96e669c5c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new fc22f36bc5b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new c9e538e2cc9 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 16ffac5697b 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new bb27a3b6f4d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 8a062718e03 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 0aabcb25e55 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 2bd4220bce9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new e4091ea568c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 34c30b07125 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 8348aabad03 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d50dbdcac77 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 26432ab2a5f 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 8f05b2b3e7d 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new dbe366a3c33 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new cd19928b717 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new cf783bc06a8 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new d946e6af7ae 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 521c944cc82 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 2fcef714953 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new c8106e083db 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new a371bec5e41 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 3600dd6a21d 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 7b1e896e933 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new d41160bafb9 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 970b41d7204 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 99601156e31 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new d60f57a59e2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 35908cbb448 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 5956ff39ff5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 0cf999d458c 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 384fd3accb8 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new b03b9bb4c4b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new bc95851d58f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 45ba264f431 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new ed4fe90033c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 93dc9b0b60b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 3839428e3cd 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new d1138cea3cc 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new fd2bb5678e4 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new c0be3da3771 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new c5d8c26b51d 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 936aa5ba9ed 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 794b3e37359 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new db7792aa779 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f22abe7640b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 00c8e357df1 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new cd90d6b26a3 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ab59d262697 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0e18882e1e0 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0678c7c920c 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 14489559b83 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9a4ca8d191b 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7fa8007cd48 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ddb2bdfb8de 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new f33c6d290db 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2cdba045d07 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new e13d27959e0 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f122b0dfac5 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new fd38f91c023 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 44245a7327f 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b3763cd7613 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits

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 (f41046d2139) \ 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 1760 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38920 -> 38684 bytes 04-build_abe-gcc/console.log.xz | Bin 204328 -> 204252 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 245436 -> 244928 bytes 08-build_abe-gdb/console.log.xz | Bin 38276 -> 38128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2384 -> 2380 bytes 11-check_regression/console.log.xz | Bin 5764 -> 5328 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/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++++----------- sumfiles/gdb.log.xz | Bin 11908 -> 11912 bytes sumfiles/gdb.sum | 30 +++++++++++++-------------- 23 files changed, 57 insertions(+), 57 deletions(-)