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-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O3_LTO.

discards 3d0cfb42 onsuccess: #108: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 106bd748 onsuccess: #107: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards e82cd772 onsuccess: #100: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards c90b7c5d onsuccess: #99: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 42b21211 onsuccess: #99: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 74271b5b onsuccess: #100: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 82cbb741 onsuccess: #107: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 2d35f9b2 onsuccess: #108: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]

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 (3d0cfb42) \ 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: