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-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts.
discards f82a24a5 4: update: llvm-0880b9d52620ca3c46456095f6040a2e4de6c871: 20358 discards 3de82992 3: reset: llvm-dc969061c68e62328607d68215ed8b9ef4a1e4b1: 20331 discards ec552f1d 2: update: qemu-39e19f5f67d925c60278a6156fd1776d04495a93: 20387 new db841be5 2: update: binutils-llvm-linux-qemu: 20387
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 (f82a24a5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 1692 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29692 -> 29952 bytes 04-build_kernel_llvm/console.log.xz | Bin 62912 -> 62100 bytes 05-build_abe-qemu/console.log.xz | Bin 33620 -> 32508 bytes 06-build_linux/console.log.xz | Bin 22780 -> 4992 bytes 08-check_regression/console.log.xz | Bin 484 -> 484 bytes 09-update_baseline/console.log | 195 +++++++++++++++++++++++++++++------ jenkins/manifest.sh | 19 ++-- results | 2 +- 10 files changed, 176 insertions(+), 40 deletions(-)