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-allnoconfig in repository toolchain/ci/base-artifacts.
discards 16e7d6b6b 0: update: binutils-gcc-linux-qemu: boot new 8ab9ca035 0: update: binutils-gcc-linux-qemu: boot
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 (16e7d6b6b) \ 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 1568 -> 1560 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 43380 -> 43960 bytes 04-build_abe-stage1/console.log.xz | Bin 71644 -> 71680 bytes 05-build_abe-qemu/console.log.xz | Bin 30608 -> 30532 bytes 06-build_linux/console.log.xz | Bin 3512 -> 3480 bytes 08-check_regression/console.log.xz | Bin 524 -> 412 bytes 08-check_regression/results.regressions | 2 -- 09-update_baseline/console.log | 13 ++++--------- 09-update_baseline/results.regressions | 2 -- jenkins/manifest.sh | 22 +++++++++++----------- 11 files changed, 15 insertions(+), 24 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 09-update_baseline/results.regressions