This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards 4d686d329 linux-f531bf6f8e5e0b928981d5d056d9aa15cdbe1605: 16511 discards d1f797c83 llvm-1407b71dceef21dcdd75dfd72c2b76fd484db943: 16549 new e79cfb22b linux-a790195efdddfc013e1ec4a95452863dab4a8fc9: 16587
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 (4d686d329) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-aarch [...]
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 1 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: 1-reset_artifacts/console.log | 255 +- 2-build_llvm/build-ok | 0 2-build_llvm/console.log | 10063 +++++++++++++++++---------------- 3-count_linux_objs/console.log | 1220 ++-- 4-check_regression/console.log | 17 +- 5-update_baseline/console.log | 34 +- console.log | 11607 +++++++++++++++++++-------------------- distance-to-baseline | 2 +- jenkins/build-name | 2 +- jenkins/manifest.sh | 24 +- results | 6 +- trigger-bisect-on-failure | 4 +- 12 files changed, 11587 insertions(+), 11647 deletions(-) delete mode 100644 2-build_llvm/build-ok