This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts.
discards 4a125ed3 4: update: binutils-gcc-linux-qemu: 21318 discards 0ac4f3dc 3: reset: linux-519ed0ab5f8b14eee1672959a65ef1d89db88c6e: 21318 discards 434169c9 2: update: binutils-gcc-qemu: 21320 new e7ae5c43 2: update: binutils-gcc-linux-qemu: 21354
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 (4a125ed3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 1592 -> 1576 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30444 -> 30724 bytes 04-build_abe-stage1/console.log.xz | Bin 72188 -> 71672 bytes 05-build_abe-qemu/console.log.xz | Bin 31284 -> 30484 bytes 06-build_linux/console.log.xz | Bin 46728 -> 43044 bytes 08-check_regression/console.log.xz | Bin 492 -> 488 bytes 09-update_baseline/console.log | 240 ++++++++++++++++++++--------------- jenkins/manifest.sh | 20 +-- results | 2 +- 10 files changed, 152 insertions(+), 110 deletions(-)