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 ca00b6ef22f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards 29b878ea63b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards d4838f45869 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards fbc17d39d7e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 237f52df399 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 45415cc7be7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards e677cf76c81 121: force: #26: : Failure after baseline build: no new commits discards ed52eadcb3f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 14a473cddb8 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 12c0271cba3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 08301457f71 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 01d1723e00a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 906c0e06466 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 51df27ccb4c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 84f44244578 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 7f930572e12 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 23ac64a7392 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 99999ffdd9a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards aa1f39a1e2a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 053e78ecd74 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 1ff93b2f29f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2a2a65be538 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards b41f36ed7dd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 79329742227 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 64105ca7db9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e343a67a8a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards a5cdbd659db 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 71bf6b08a81 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards f8ddfe5f125 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 7ac64261d87 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 0562cfdae37 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e84153f3da3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 1e87fa39656 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 76b904bb0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards e499eda7fc4 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards d68c968182e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d61469e804c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 3a81762ee80 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 99a90110c16 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards ded065539f7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 59129e3d537 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards d21652521e7 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards b1961f30678 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0afc14c2d68 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards c273cce8c2c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards bda3fb54cbd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards f50d42494f6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards f9b150aa66b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards dd75ad0f738 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards eccd1bb9eb9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards d6695a11ae3 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 604091260a1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards ac7092bab31 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards bf91c7267a6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards d221f97ed2a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 5ef0e0f9035 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards c187d811812 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 4a0ed7cae5e 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 19a73dd0fa3 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 6b81bd48477 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards b9e12b786b3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 3b2443b57f0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 4832c9ad324 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 498c3dd6132 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 9f54d23fcbf 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards b366e701a2c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 223d641ae70 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards d9d30391bd3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 6f1401f8f30 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards f89a9f4f4b4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards da878a73483 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards eff73f64b36 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards a2b26326f34 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 72c16ac9a6f 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 03278fbacc0 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 1a6e0f9a41c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 95ee6ed6228 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards d1a732b97cd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards f45c01a0a47 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 43c76c4f3f4 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards de55557b214 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards d83eba0b4bb 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 62f5e4c105f 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 5d97ff68a98 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards dfb38c31f65 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 5e5230d4833 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 987c44a82f0 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards a36fc0e7553 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 281d5aa2829 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 96330b3f189 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 9bf61c3552d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards bc79b138010 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 7a8f8f27bdc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 529981d3698 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3a2bd564e14 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 293489ebb5f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards a448c8dc51d 31: onsuccess: #38: 1: Success after linux: 14 commits discards 5a83f9231b5 30: onsuccess: #36: 1: Success after binutils: 18 commits discards a31ab09e0d6 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c184843ab87 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards c210536ec47 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 78ab64da314 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d343c3750a8 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 167ddfe1708 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new fab2f2609c9 30: onsuccess: #36: 1: Success after binutils: 18 commits new fccc8606ba7 31: onsuccess: #38: 1: Success after linux: 14 commits new 920609e3c0f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 636ad4e955f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 38a9e663c18 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 23b0ed60088 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3fcfcdbb7e5 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 946fe28bd02 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new a5d3bc5a987 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new b6d8f584dd6 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 718316e7efa 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new dac14868292 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new bb82e94b17b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 4ae8477ce9c 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new e5ee13ce1e8 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new add17c65b64 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new cb3deb38d78 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 27c5d9ac966 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 9ffe595e80d 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 53643acfb4d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 97da59688e4 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 91e3a7aacea 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 8d2eb04f3c1 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new df2f1fa689b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 94c12e3a55b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 29cac887ef5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 47a6f19d668 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 52c8506a67b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new bb69372bafd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new ae86c93d762 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 5cc3b040b43 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 0200db2209a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 916b4485d58 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 931fa6c5e48 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 7c230f96cb6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 91f10add322 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 7a3b5f70ca9 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 0363f498861 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new d4cc3b98ffb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 7d58ef804d8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 86466ec1093 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 65a3a4e60ee 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new bfaf78ce159 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 9a8cdf6dd1c 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 5609c5d0508 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 1ea502cdbb0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 07be1891b49 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 42d74e7c0f8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new fea7b0cbf45 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 508bc654941 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 05db0bd38c6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 1dd02fbbfe3 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 1fc66d1a964 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new e7a2e32f986 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 7263dd2da8e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new abe60845245 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 65b89a098ca 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new b75fef90834 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 4598c66f654 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 7338c9d0361 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new a08851c1dbb 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new d7e34e227ce 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new a3bbb82f0ca 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 2957932a16f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new e84649db06a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 59df9662baf 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new ef894bf915e 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 65bd6542433 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 92044746889 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 26a09dbd192 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new d1df5fe31da 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new cf41b2eb722 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 5950c0eb58a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new f1bc72cd77b 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4ff04ad3984 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new d2b86dd6ce4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 27285f9e6ac 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new fc73bdd8f86 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4665f9792fb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new a51cf465876 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new beae34a16e8 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 912e877b786 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3cf696a69ce 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 68de6afa2bf 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 17ef2313aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b7b1f7e4518 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7d73c6853cd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 441d2f8b9af 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 3d6adacec46 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 8a4d3069fe2 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new df1060f7573 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b6e41f765e0 121: force: #26: : Failure after baseline build: no new commits new b08950a9893 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f693aacd9bd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 15d34b834dc 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new f2accf4d3a2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f434429d0ee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 2679fe0ac50 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new a0aba751884 128: onsuccess: #34: 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 (ca00b6ef22f) \ 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 2064 -> 2140 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49316 -> 49076 bytes 04-build_abe-gcc/console.log.xz | Bin 238844 -> 236716 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 232792 -> 232340 bytes 08-build_abe-gdb/console.log.xz | Bin 46776 -> 47396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2712 -> 2732 bytes 11-check_regression/console.log.xz | Bin 5072 -> 4816 bytes 11-check_regression/results.compare2 | 4 ++-- 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 | 34 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14468 -> 14468 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 48 insertions(+), 48 deletions(-)