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 bbef7bfbec7 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 08c0bf8ee30 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards 19144de60e5 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 113b875bb7e 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 8457600baf2 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards d17a37b618c 127: force: #27: : Failure after baseline build: no new commits discards aec974c49d7 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a7ac285265e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9ca8fc490ca 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 5b6ece75662 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards cc334b0eb7c 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 90c4f589596 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6f996533dc1 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards be99343ec93 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 679f0e1cb71 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 1cdba15e0bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 96a76bba6a8 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 8dc129c00f9 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ca0dfe6a1cb 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b77eab047be 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 8e4d4654247 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f97919c051b 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 74179861e0e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 041bafba961 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards e9495f92366 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards c14efa762f2 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 959957ba458 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards c309da8fda6 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 90999730e99 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 7a38b916f92 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 96b3b0a01b9 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 6175b7e7187 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 2ca5e6d6b4a 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 5e802258ab7 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 33be81c96c8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 62c883fc55a 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 3e5ee855bb0 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 7ee6f199de4 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards dfe282fb0e9 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 2cbd5d26ea8 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 8172b0ad83b 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 91d08a73de8 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 3b9158c2d21 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 807cde2386c 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 9fbd063b9d6 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 5c70f7f6693 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 87cb472dcdc 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 3c388f09233 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards db3381f1fba 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards b7aea5a36c0 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 0f82b962b92 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 0a607209a45 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards f1c9e829264 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 36c57f97bc8 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 043d7242ef2 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards a122a27a844 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards e1ae33b4871 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 8ae8a4cdb67 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards bc0849702e0 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 9262b37081c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 1e5f798f904 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 44ef44cbb03 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards f5320c58ea3 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards 2274242cefa 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 6e8d8a58cb6 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 83b2d2deb71 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 47b5092bda7 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards c0356d26ef0 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards c9c59bad0c3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 48c55ee53bf 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 75357542965 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 398b0600ca5 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 1d9f14c3e0a 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 424d9218e53 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 32791528f40 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 9c4336c1b6a 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 1867cd97d03 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 4b9ebf9304b 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards a99940a67d3 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards dfcfa7898d8 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards d79b301ca9e 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards e06515f9810 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 5b28fe0668a 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards b794a9f8296 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 6230671046c 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards bb71f39b8a5 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 03747767f5a 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards d884d50215c 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards e9d2b9b3084 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards b78058a7f69 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 9d7d14850dc 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 8d9c5cc5f30 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 05db29ca0af 40: onsuccess: #49: 1: Success after linux: 219 commits discards d590e8ddd40 39: onsuccess: #48: 1: Success after glibc: 2 commits discards be098eed450 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 6f58c0a01cc 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards fc9996690fc 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 89e590986a1 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 5aebd60ec94 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 9460dea4a2a 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards e3eb851a20e 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 4b0a2bad91f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new d3775711081 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new e2ad1121226 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 90453d0789a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new f626f2b3c1f 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new a6107c03dfb 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 2b720e5d75a 38: onsuccess: #46: 1: Success after binutils: 26 commits new 36bdeedce74 39: onsuccess: #48: 1: Success after glibc: 2 commits new c4a2de43ca9 40: onsuccess: #49: 1: Success after linux: 219 commits new 89edf88993e 41: onsuccess: #51: 1: Success after binutils: 12 commits new b03945e2e4d 42: onsuccess: #53: 1: Success after linux: 3008 commits new ed449dc3d55 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new db5e62fc507 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new bb179219f5d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 884aa71f261 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 121bb9be834 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 634d48f63c5 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new cb7598cf7e1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new fe51c38a81d 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new fb939c87a0f 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new b8391e57c28 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new d4f0beb6431 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new b10e7f74a3a 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new fe794f9d233 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 7564e1e1258 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 2f861d288d4 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 1b9ff34b346 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 87567b814e0 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new d85427ecf6b 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new 74adf5f5d35 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 51d59ad8f8e 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 103cc9d9277 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 735c62e4020 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new c38801e7bd3 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new f951475447c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 953008a9eac 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new f01cfb14237 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new c3fc1ce10b0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new aefedddc163 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new d73079dbd72 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new a782435972a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 61a1996ff16 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 7f696c0ae57 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 63ba30bfcc8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 428a35b6a68 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 3b562d4966a 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 19d5846465e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 83731e8b388 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 51bfabf8b28 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 35c0aade175 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 1b0e98d4d10 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 00bf21b16fe 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new e52a8213569 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new a696870aabb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 8400a0a465c 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 03f91c22eb7 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 942030ab9ed 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new b5b910c3691 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 34714301ed2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 422460dbae8 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 9daf54b8b7b 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new e33a2ecc611 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new fb240ffa7a2 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 377e028928e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 165dc41419b 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new cd9bc454958 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new e0829460017 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new f0cd2f1d860 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new a77c207123b 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 714f38b634e 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 927bcdb5b6f 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 88444ff3c07 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new ece0e5dcefa 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 94eed5c944c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 57f8c7443fc 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new d1a50839a70 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6ecae68b714 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 0ae52a597d3 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new cd2119076d9 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d950d924680 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 633f737efc7 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 9413bcb4a15 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 3ada2b89fd4 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new daa782fd4fa 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 77e174ab942 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a7f6603e0cc 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 368f6a034d5 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2ca0c38e560 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 7013f5c49cf 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 650bfcd258e 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 100114824ed 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 1b778ea9b65 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new f4b346bc46c 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new c54ea11bb5d 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b77cdbc3f13 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 4f4aa9694ae 127: force: #27: : Failure after baseline build: no new commits new 1d96838b10a 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new e233e559368 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new d2ef07f71eb 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 23787f01c9c 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new 6f21bb11fb1 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 675b88c5da1 133: onsuccess: #36: 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 (bbef7bfbec7) \ 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 2028 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35096 -> 34972 bytes 04-build_abe-gcc/console.log.xz | Bin 203780 -> 203808 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8488 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 240732 -> 240976 bytes 08-build_abe-gdb/console.log.xz | Bin 34808 -> 34548 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2732 -> 2816 bytes 11-check_regression/console.log.xz | Bin 4728 -> 4696 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 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/linux_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14632 -> 14668 bytes sumfiles/gdb.sum | 4 +- 27 files changed, 66 insertions(+), 68 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt