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_size-cpu2017rate/llvm-arm-master-Oz in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-Oz.

discards 140b8c4c onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 4cef7d56 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards df1aebc2 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards b9f684c0 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new b0bbfdd7 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 2ffcd72b onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 03f3813d onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e6fe2b6e onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]

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 (140b8c4c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]

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: