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-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards c6d82ad65 4: update: binutils-llvm-linux-qemu: 20179 discards 34ea54c10 3: reset: linux-76657eaef4a759e695eb1883d4f1d9af1e4ff9a8: 20062 discards 8712f46ac 2: update: binutils-llvm-qemu: 20182 new 432df36d5 2: update: binutils-llvm-linux-qemu: 20193
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 (c6d82ad65) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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 1736 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30108 -> 30108 bytes 04-build_llvm/console.log.xz | Bin 60188 -> 60224 bytes 05-build_abe-qemu/console.log.xz | Bin 30240 -> 30524 bytes 06-build_linux/console.log.xz | Bin 5576 -> 5800 bytes 08-check_regression/console.log.xz | Bin 484 -> 484 bytes 09-update_baseline/console.log | 113 ++++++++++++++++++++++++++++++----- jenkins/manifest.sh | 20 +++---- results | 2 +- 10 files changed, 110 insertions(+), 25 deletions(-)