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

discards 18cb722f 6: update: binutils-gcc-linux-qemu: 21462 discards b775aa06 5: reset: gcc-9d6a0f388eb048f8d87f47af78f07b5ce513bfe6: 21457 discards 14a8d929 4: update: qemu-6621441db50d5bae7e34dbd04bf3c57a27a71b32: 21486 new d6c4d811 4: update: binutils-gcc-linux-qemu: 22133

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 (18cb722f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]

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 1580 -> 1592 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29992 -> 30688 bytes 04-build_abe-stage1/console.log.xz | Bin 90784 -> 90532 bytes 05-build_abe-qemu/console.log.xz | Bin 30628 -> 30884 bytes 06-build_linux/console.log.xz | Bin 45808 -> 9008 bytes 08-check_regression/console.log.xz | Bin 480 -> 484 bytes 09-update_baseline/console.log | 96 +++++++++++++++++++++++++---------- jenkins/manifest.sh | 22 ++++---- results | 2 +- 10 files changed, 81 insertions(+), 39 deletions(-)