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-allmodconfig in repository toolchain/ci/base-artifacts.
discards e5e86c19 5: update: llvm-95b2aa511eea1f31e183a2a3aed4d2aa852d089c: 40 new d910443c 5: update: linux-109f6d10ec17302c4666f7df3dfa0e31d8589d41: 40
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 (e5e86c19) \ 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: 01-reset_artifacts/console.log.xz | Bin 1612 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30128 -> 29500 bytes 04-build_llvm/console.log.xz | Bin 62408 -> 63092 bytes 05-build_abe-qemu/console.log.xz | Bin 32656 -> 32676 bytes 06-build_linux/console.log.xz | Bin 5344 -> 3784 bytes 08-check_regression/console.log.xz | Bin 476 -> 472 bytes 09-update_baseline/console.log | 216 +++++++++++++++++------------------ jenkins/manifest.sh | 10 +- 9 files changed, 113 insertions(+), 113 deletions(-)