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 8cf02a84 4: update: llvm-4022551a154e01ca5347629fd429ca04b36801e0: 37 discards 0d3a0284 3: reset: llvm-6f348b146b69a50d5fb1b9fbfd14bc1d204e45c4: 37 discards 88bce8e8 2: update: qemu-a28498b1f9591e12dcbfdf06dc8f54e15926760e: 20742 new f46a2c72 2: update: binutils-llvm-linux-qemu: 20757
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 (8cf02a84) \ 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 1608 -> 1604 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29312 -> 30808 bytes 04-build_kernel_llvm/console.log.xz | Bin 62560 -> 62544 bytes 05-build_abe-qemu/console.log.xz | Bin 33148 -> 33184 bytes 06-build_linux/console.log.xz | Bin 5600 -> 5588 bytes 08-check_regression/console.log.xz | Bin 476 -> 508 bytes 09-update_baseline/console.log | 215 ++++++++++++++++++++++++----------- jenkins/manifest.sh | 19 ++-- results | 2 +- 10 files changed, 162 insertions(+), 74 deletions(-)