This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts.

discards c2c142ab 4: update: binutils-llvm-linux-qemu: 20383 discards 278d1706 3: reset: llvm-5955a0f9375a8c0b134eeb4a8de5155dcce7c94f: 20364 discards c5932bf6 2: update: qemu-731340813fdb4cb8339edb8630e3f923b7d987ec: 20385 new d2c7a61d 2: update: binutils-llvm-linux-qemu: 20407

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 (c2c142ab) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-m [...]

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 1576 -> 1600 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30292 -> 30416 bytes 04-build_llvm/console.log.xz | Bin 61260 -> 61608 bytes 05-build_abe-qemu/console.log.xz | Bin 31576 -> 31708 bytes 06-build_linux/console.log.xz | Bin 4628 -> 4568 bytes 08-check_regression/console.log.xz | Bin 476 -> 488 bytes 09-update_baseline/console.log | 122 +++++++++++++++++++++++------------ jenkins/manifest.sh | 22 +++---- results | 2 +- 10 files changed, 94 insertions(+), 52 deletions(-)