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-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts.
discards 223583f3e 2: update: binutils-llvm-linux-qemu: 19716 new 38e200515 2: update: binutils-llvm-linux-qemu: 19716
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 (223583f3e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 1608 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 41528 -> 41920 bytes 04-build_llvm/console.log.xz | Bin 57296 -> 58020 bytes 05-build_abe-qemu/console.log.xz | Bin 29948 -> 30328 bytes 06-build_linux/console.log.xz | Bin 4632 -> 4968 bytes 08-check_regression/console.log.xz | Bin 540 -> 508 bytes 08-check_regression/results.regressions | 2 - 09-update_baseline/console.log | 161 ++++++++++++++++---------------- jenkins/manifest.sh | 22 ++--- 10 files changed, 91 insertions(+), 94 deletions(-) delete mode 100644 08-check_regression/results.regressions