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 7771e954 4: update: binutils-gcc-linux-qemu: 21325 discards 8b972513 3: reset: gcc-9d6a0f388eb048f8d87f47af78f07b5ce513bfe6: 21324 discards 2a378ecb 2: update: qemu-69353c332c558cead5f8081d0bb69f989fe33fa3: 21354 new 46955e7f 2: update: binutils-gcc-linux-qemu: 22010

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 (7771e954) \ 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 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30012 -> 32872 bytes 04-build_abe-stage1/console.log.xz | Bin 71492 -> 71528 bytes 05-build_abe-qemu/console.log.xz | Bin 31640 -> 31364 bytes 06-build_linux/console.log.xz | Bin 48304 -> 10516 bytes 08-check_regression/console.log.xz | Bin 476 -> 480 bytes 09-update_baseline/console.log | 258 ++++++++++++++++++++--------------- jenkins/manifest.sh | 22 +-- results | 2 +- 10 files changed, 162 insertions(+), 120 deletions(-)