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-allmodconfig in repository toolchain/ci/base-artifacts.
discards 971584472 5: update: binutils-gcc-linux-qemu: 21325 discards d85968e53 4: reset: gcc-9d6a0f388eb048f8d87f47af78f07b5ce513bfe6: 21324 discards f7ed9e256 3: update: qemu-1cd2ad11d37c48f284f557954e1df675b126264c: 21354 new 4f54dd1fe 3: update: binutils-gcc-linux-qemu: 21526
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 (971584472) \ 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 1872 -> 1596 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30412 -> 30496 bytes 04-build_abe-stage1/console.log.xz | Bin 71368 -> 71368 bytes 05-build_abe-qemu/console.log.xz | Bin 31356 -> 31484 bytes 06-build_linux/console.log.xz | Bin 47940 -> 48176 bytes 08-check_regression/console.log.xz | Bin 480 -> 484 bytes 09-update_baseline/console.log | 173 ++++++++++++++++++++++++++--------- jenkins/manifest.sh | 20 ++-- results | 2 +- 10 files changed, 142 insertions(+), 53 deletions(-)