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-mainline-defconfig in repository toolchain/ci/base-artifacts.
discards 6aa235ca23 linux-d47e3da1759230e394096fd742aad423c291ba48: 5082 discards a3b65d87ea linux-cc9f8349cb33965120a96c12e05d00676162eb7f: 4972 new 303b59a8c7 1: last-good: llvm-e47f89cb2cba7f6441b851ac43a22d989ce5bb51: 5082
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 (6aa235ca23) \ 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 | 70 +- 2-build_llvm/console.log | 10283 ++++++++++++++++++------------------- 3-count_linux_objs/console.log | 199 +- 4-check_regression/console.log | 2 +- 5-update_baseline/console.log | 14 +- console.log | 10568 +++++++++++++++++++-------------------- distance-to-baseline | 1 - jenkins/build-name | 1 - jenkins/manifest.sh | 29 +- trigger-bisect-on-failure | 3 - 10 files changed, 10560 insertions(+), 10610 deletions(-) delete mode 100644 distance-to-baseline delete mode 100644 jenkins/build-name delete mode 100644 trigger-bisect-on-failure