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 4a374ba3c59 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 945188c87ae 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 4f8959d77e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 783ca66f54f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ccd3da37df5 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 64954ec0b8d 121: force: #26: : Failure after baseline build: no new commits discards f7199dd487b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0115578abca 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9c74ea06f8c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7a1a0ca1702 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 049594f70f7 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 64128a95bc5 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7e9588c6197 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e5ea0f11563 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 5a130adec6a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f05afdd0e98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 015f2554d5d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c2681bff147 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0abb993e7d5 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 431d8bbe77f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 90bc1e2b682 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards f4185230599 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8826822e8e1 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 9613a3be5ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 33006f21542 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 8b4ffc73464 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 400bdb7c8ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards f545fc72c59 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards a4c2b93ac30 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards dc42a7daca9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 5e0d7aac85c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 306d1286de3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 218076dbd97 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards b375cc723d6 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 3b038ad3567 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards cfb20c6745e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 098433c78d5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 499e679d042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 6405a579831 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards afe0e01e0e3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards befe4a06a45 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5c095f5e99e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0cd2e5a9d15 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 69096adc431 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards c6a9185ef27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 6bdd989ff53 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards b2ae59eb7b4 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 84bced38dba 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards fe0ba61e3b3 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 7de90d3ee18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 8e38416075b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 95219e8f0e3 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 8a5d54b61f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 5e7676bc950 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 8a6bc21de03 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 0ba7ff1477f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards f1ff92b60ed 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards b70c2610d5b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 51b245e1ad0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards cfcce76c26c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 8f8936bff8e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 772399ee81c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 526daaa5304 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 325630e5bc2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fdcd8a88382 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 6d722f1fcb1 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards aea0fb3081c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 3c2b0f1461c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 9ca0d04b3cb 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 5b65b52afaf 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 52f152528d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards a13248c22fd 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards fa42c2ffd48 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards b6caa2fb3ac 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards fe99a0c8088 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards c17ed7c38b3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e7bc4e03c7b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 702c090e7b2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 193b596ce39 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 2aa883eceba 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b78409c09dd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 513483c35f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 83ea3976bd7 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards bda4812f4ed 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards e6ed15f3183 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards d40c359869f 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 376b8376091 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards e8f89c7e4a9 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 8e151fc684c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 8909ccb23a1 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards f1b0efeef2d 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards a5fd0776c24 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 0d94bb59577 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 7d411e0d92b 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 9b1b1ccfdc7 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 85c7fbf8b01 31: onsuccess: #38: 1: Success after linux: 14 commits discards 2e70113ce38 30: onsuccess: #36: 1: Success after binutils: 18 commits discards c5f7a147c55 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards f0b5ba5f155 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards ff1fdc961bb 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards dfbfd2bc09b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new cdbe02c864f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c210536ec47 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new c184843ab87 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new a31ab09e0d6 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 5a83f9231b5 30: onsuccess: #36: 1: Success after binutils: 18 commits new a448c8dc51d 31: onsuccess: #38: 1: Success after linux: 14 commits new 293489ebb5f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3a2bd564e14 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 529981d3698 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 7a8f8f27bdc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new bc79b138010 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 9bf61c3552d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 96330b3f189 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 281d5aa2829 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new a36fc0e7553 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 987c44a82f0 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 5e5230d4833 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new dfb38c31f65 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 5d97ff68a98 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 62f5e4c105f 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new d83eba0b4bb 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new de55557b214 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 43c76c4f3f4 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new f45c01a0a47 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new d1a732b97cd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 95ee6ed6228 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 1a6e0f9a41c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 03278fbacc0 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 72c16ac9a6f 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new a2b26326f34 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new eff73f64b36 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new da878a73483 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new f89a9f4f4b4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 6f1401f8f30 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new d9d30391bd3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 223d641ae70 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new b366e701a2c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 9f54d23fcbf 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 498c3dd6132 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 4832c9ad324 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 3b2443b57f0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new b9e12b786b3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 6b81bd48477 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 19a73dd0fa3 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 4a0ed7cae5e 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new c187d811812 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 5ef0e0f9035 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new d221f97ed2a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new bf91c7267a6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new ac7092bab31 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 604091260a1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new d6695a11ae3 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new eccd1bb9eb9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new dd75ad0f738 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new f9b150aa66b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new f50d42494f6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new bda3fb54cbd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new c273cce8c2c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 0afc14c2d68 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new b1961f30678 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d21652521e7 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 59129e3d537 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new ded065539f7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 99a90110c16 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 3a81762ee80 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new d61469e804c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new d68c968182e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new e499eda7fc4 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 76b904bb0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 1e87fa39656 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e84153f3da3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 0562cfdae37 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 7ac64261d87 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new f8ddfe5f125 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 71bf6b08a81 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new a5cdbd659db 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new e343a67a8a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 64105ca7db9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 79329742227 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new b41f36ed7dd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2a2a65be538 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 1ff93b2f29f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 053e78ecd74 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new aa1f39a1e2a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99999ffdd9a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 23ac64a7392 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7f930572e12 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 84f44244578 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 51df27ccb4c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 906c0e06466 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 01d1723e00a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 08301457f71 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 12c0271cba3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 14a473cddb8 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ed52eadcb3f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e677cf76c81 121: force: #26: : Failure after baseline build: no new commits new 45415cc7be7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 237f52df399 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new fbc17d39d7e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new d4838f45869 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 29b878ea63b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ca00b6ef22f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...]
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 (4a374ba3c59) \ 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 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 49020 -> 49316 bytes 04-build_abe-gcc/console.log.xz | Bin 236288 -> 238844 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8404 -> 8408 bytes 07-build_abe-glibc/console.log.xz | Bin 232820 -> 232792 bytes 08-build_abe-gdb/console.log.xz | Bin 47588 -> 46776 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2916 -> 2712 bytes 11-check_regression/console.log.xz | Bin 4772 -> 5072 bytes 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/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++---------- sumfiles/gdb.log.xz | Bin 14476 -> 14468 bytes sumfiles/gdb.sum | 4 +- 26 files changed, 69 insertions(+), 69 deletions(-)