This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-arm-master-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-cpu2017rate/llvm-arm-master-O3.
discards f3c9f584 force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] discards f4a7d055 onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 9d8c2cb2 force: #74: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] discards ac104bd2 onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 85c96c46 onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new cb348172 force: #74: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] new 863b2b01 onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 22b8063c force: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...]
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 (f3c9f584) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-cpu2017ra [...]
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 4 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: