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-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards 80f26ddff 2: update: binutils-llvm-linux-qemu: 20647 new 2024298f6 2: update: binutils-llvm-linux-qemu: 20654
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 (80f26ddff) \ 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 1556 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 29844 -> 30436 bytes 04-build_kernel_llvm/console.log.xz | Bin 0 -> 61788 bytes 04-build_llvm/console.log.xz | Bin 60492 -> 0 bytes 05-build_abe-qemu/console.log.xz | Bin 31468 -> 31496 bytes 06-build_linux/console.log.xz | Bin 5736 -> 5700 bytes 08-check_regression/console.log.xz | Bin 480 -> 484 bytes 09-update_baseline/console.log | 238 +++++++++++++++++------------------ jenkins/manifest.sh | 18 +-- results | 4 +- 11 files changed, 130 insertions(+), 130 deletions(-) create mode 100644 04-build_kernel_llvm/console.log.xz delete mode 100644 04-build_llvm/console.log.xz