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-stable-allyesconfig in repository toolchain/ci/base-artifacts.
discards deff37eb 5: update: binutils-gcc-linux-qemu: 19623 discards 2d3d3ae5 4: reset: linux-519ed0ab5f8b14eee1672959a65ef1d89db88c6e: 19623 discards d1dc4c82 3: update: binutils-gcc-qemu: 19624 new 2f48b7b3 3: update: binutils-gcc-linux-qemu: 19651
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 (deff37eb) \ 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 1572 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30164 -> 31412 bytes 04-build_abe-stage1/console.log.xz | Bin 71648 -> 72768 bytes 05-build_abe-qemu/console.log.xz | Bin 31224 -> 31112 bytes 06-build_linux/console.log.xz | Bin 46516 -> 43288 bytes 08-check_regression/console.log.xz | Bin 480 -> 480 bytes 09-update_baseline/console.log | 187 ++++++++++++++++++++++++++--------- jenkins/manifest.sh | 20 ++-- results | 2 +- 10 files changed, 149 insertions(+), 60 deletions(-)