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-release-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts.
discards 2f12aa46 4: update: binutils-gcc-linux-qemu: 22040 discards 7ff04d98 3: reset: linux-caba66ec322e22a65c388ae81b23942c7f51f982: 22040 discards 6830e51c 2: update: binutils-gcc-qemu: 22042 new 26e66bb4 2: update: binutils-gcc-linux-qemu: 22042
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 (2f12aa46) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 -> 1576 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30320 -> 30432 bytes 04-build_abe-stage1/console.log.xz | Bin 68224 -> 68280 bytes 05-build_abe-qemu/console.log.xz | Bin 32820 -> 32460 bytes 06-build_linux/console.log.xz | Bin 6548 -> 6008 bytes 08-check_regression/console.log.xz | Bin 484 -> 480 bytes 09-update_baseline/console.log | 204 +++++++++++++++++++++++++---------- jenkins/manifest.sh | 22 ++-- results | 2 +- 10 files changed, 159 insertions(+), 69 deletions(-)