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-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards 661f306d9 2: update: linux-7c5e07b73ff3011c9b82d4a3286a3362b951ad2b: 20866 new 0499955b8 2: update: binutils-gcc-linux-qemu: 20879
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 (661f306d9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]
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 1692 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29820 -> 30336 bytes 04-build_abe-stage1/console.log.xz | Bin 88224 -> 86256 bytes 05-build_abe-qemu/console.log.xz | Bin 32548 -> 31880 bytes 06-build_linux/console.log.xz | Bin 4760 -> 4912 bytes 08-check_regression/console.log.xz | Bin 484 -> 480 bytes 09-update_baseline/console.log | 101 +++++++++++++++++++++++++---------- jenkins/manifest.sh | 19 ++++--- results | 2 +- 10 files changed, 84 insertions(+), 38 deletions(-)