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-release-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts.
discards 7ddff74af 2: update: binutils-llvm-linux-qemu: 20894 new 471fbd50b 2: update: binutils-llvm-linux-qemu: 20965
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 (7ddff74af) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 1580 -> 1564 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30348 -> 30184 bytes 04-build_kernel_llvm/console.log.xz | Bin 0 -> 60928 bytes 04-build_llvm/console.log.xz | Bin 61792 -> 0 bytes 05-build_abe-qemu/console.log.xz | Bin 32116 -> 32276 bytes 06-build_linux/console.log.xz | Bin 4676 -> 4072 bytes 08-check_regression/console.log.xz | Bin 476 -> 484 bytes 09-update_baseline/console.log | 224 +++++++++++++++++------------------ jenkins/manifest.sh | 18 +-- results | 4 +- 11 files changed, 123 insertions(+), 123 deletions(-) create mode 100644 04-build_kernel_llvm/console.log.xz delete mode 100644 04-build_llvm/console.log.xz