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-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts.

discards f7543834a 3: update: binutils-gcc-linux-qemu: 20119 discards d6ae46b6e 2: reset: gcc-a25e0b5e6ac8a77a71c229e0a7b744603365b0e9: 19439 new 10ce0e1d5 2: update: binutils-gcc-linux-qemu: 20256

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 (f7543834a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-s [...]

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 1560 -> 1560 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29904 -> 29716 bytes 04-build_abe-stage1/console.log.xz | Bin 86052 -> 86000 bytes 05-build_abe-qemu/console.log.xz | Bin 32148 -> 32144 bytes 06-build_linux/console.log.xz | Bin 5768 -> 16576 bytes 08-check_regression/console.log.xz | Bin 480 -> 484 bytes 09-update_baseline/console.log | 125 ++++++++++++++++++++++++----------- jenkins/manifest.sh | 20 +++--- results | 2 +- 10 files changed, 97 insertions(+), 50 deletions(-)