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 94e56e60b70 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7fff17c1199 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 09e14a9b46d 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 5378a00f2d5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 90baf6abc38 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 450217574ec 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 53fdd3792c8 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 1c916f29126 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e3a6c9332ae 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards bf42f0b9d7e 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 9faa2c9ee0b 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 8051c1eeb6c 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards df3976c29a8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ee95d3f3b5a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 40831d17299 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 2aef4451a4a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 8e2521dddf8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 958f8ecef12 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards ac58c2739b3 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards ca04d4cb8b6 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards cd749a44057 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards c9aac3b59c5 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards e73c8d21ed3 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards df8c0cd17be 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 9c83b30d863 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 09e2d09d124 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 0b77835f89c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 79e0011f70b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 9a00d1c7b6d 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards bbb0b6b0c4e 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards dded606830c 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 00ae04f119e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 0c165809354 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 01d920625a0 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards c490b6f7e85 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards a2cacb7d4b6 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards b8337be3eb4 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 1bd1e5fb08f 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 00638c006c9 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards f7e3b2ed761 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards bee1da421c8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards a8e1ea0c12a 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 833e9078ede 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 2a030eeca6d 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 6765ad5d45d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards a00782720ed 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards aba1c78756e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 73b0f45bf1a 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 8cb1080352a 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards fcfb46160f3 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 40484700e6c 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 7cd216ec997 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 2ac8885d531 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 4aadf8df812 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards ff0f39da069 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 376b8455bac 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards d7ef96f841e 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards b3972e8db0f 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 1edfdb019bc 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 7eb2763cde6 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 3d09c7811ef 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards ccbcea65edb 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 084ccb78eea 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 7f6f83e9b17 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 2f169fe19e3 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards ed29ad7b549 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards f50b0141c74 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards f2365ef7636 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards e7050c07f85 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards f4da28161cd 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 8031d74d3b8 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 75b41d76dc2 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards a203eb7157d 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards f50b49c6066 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 21181307bf1 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards e5e976eed80 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 35a66e61a9c 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4500e8a372c 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 6021cb57ecc 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 06cbed7cb66 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards cfaa3cc4e0a 42: onsuccess: #53: 1: Success after linux: 3008 commits discards bd79ee73484 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 4e241541fd8 40: onsuccess: #49: 1: Success after linux: 219 commits discards a7a6d5a9ad7 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 484f07175fe 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 14ac0b52ac9 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards dfe748c0bbb 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards abd2bce1c31 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 35885b46cad 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 93ba45c729a 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards 55f1bfa83f2 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 1b95094f681 31: onsuccess: #38: 1: Success after linux: 12 commits discards c285f9390bf 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 1822b11ac06 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 3692e2405bc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 3d5f5bf62e6 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 513696e65ea 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards fd652578ef1 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 8efda3a2726 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 657da3424c1 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 615201adf73 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 80bde069ad7 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 54854bd5cd0 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 2345a69744f 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new c3748b142c4 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 7b3dc494749 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 94fba21e36b 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new e8cf734841e 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new e7cc87b4664 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 88a7f3ba5a6 30: onsuccess: #36: 1: Success after binutils: 18 commits new 56eea52ba5e 31: onsuccess: #38: 1: Success after linux: 12 commits new 64091ff268b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 552198a8768 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new a5a883e7b5a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new fba073275e5 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 2c5c2fe8597 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new c44e19c2972 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 731ffbeadf5 38: onsuccess: #46: 1: Success after binutils: 26 commits new e6793263cc4 39: onsuccess: #48: 1: Success after glibc: 2 commits new d2cdfd4057a 40: onsuccess: #49: 1: Success after linux: 219 commits new cdb1d17711a 41: onsuccess: #51: 1: Success after binutils: 12 commits new 235fd54623c 42: onsuccess: #53: 1: Success after linux: 3008 commits new de68859b4a1 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 6b9c3cf08ff 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new f68311757ec 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new b8469132ed2 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 4f01d848f50 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new ee11370fc37 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 15d8f18bfa2 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 432f77188c5 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 77e04bf96a7 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 4dc0cc34dbc 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 392fb7d7e5e 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new d7a4424beb4 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 686102c4433 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 073dcd9d21c 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 4ec1741a4f5 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new a6dfa0bfbc2 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new ec30a2b6601 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 975fecb9876 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 9aaad632f35 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new f117a0b73b9 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 2b8cfb4037f 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 36e529ea443 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new f439b18592a 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 3c7d891e945 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 6f938debb0c 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 4a7d4d31121 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new d90146e8ceb 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new aae4a4c37eb 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 1d9908c248e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 52510a38112 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 00316e892a9 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 650b9dc81c4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new df39d276d6c 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 943eed8946c 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 24beedaf640 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 804b5d616a9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new cf51b5fdf43 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new ebdcd88f755 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 2d1e63548a2 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 637f0356ee3 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 1b0219d82a0 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new b03330ecdae 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 89c2b576ae9 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 04368cc31bc 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 29e4d0d0979 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new a42c1a6c5b1 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 9971b157913 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 0ae637294af 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 623cb21b56e 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 6367729c22d 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new 8ddffd60bee 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 11f5f452b14 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new be0760b177b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new e4582ee7b82 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 492bea3fffa 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 2f3837d3753 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 0d514ca40f9 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new d8f85b364e9 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 0b29316f68c 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 454a9e47694 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new d1891db2efa 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new c9030b090f2 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 0c467757caa 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 5d10bfc9503 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 6d0438d2554 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 04fd09ea74d 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new e21bd12435b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 537766460b8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new cb2a485c24a 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d6d0ebd9f2f 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 26024481732 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 4bcd0e6bbda 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ed2879c8183 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3227e39c2c9 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e22d0f9c0b2 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 9e4897ecc2b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3765ca14394 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 564954aa957 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new fa42a6632aa 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 26f45d31d3b 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f41046d2139 123: onsuccess: #17: 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 (94e56e60b70) \ 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 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 38796 -> 38920 bytes 04-build_abe-gcc/console.log.xz | Bin 204652 -> 204328 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8788 bytes 07-build_abe-glibc/console.log.xz | Bin 244244 -> 245436 bytes 08-build_abe-gdb/console.log.xz | Bin 38488 -> 38276 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3752 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2492 -> 2384 bytes 11-check_regression/console.log.xz | Bin 6164 -> 5764 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/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 11916 -> 11908 bytes sumfiles/gdb.sum | 30 +++++++++++++-------------- 25 files changed, 63 insertions(+), 63 deletions(-)