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-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards b9278411e 4: update: llvm-0f567f0e3ed8cd76a25f49c53c2707cc7e2b2088: 19948 discards d424b6e4d 3: reset: llvm-f59cc9542bfb461d16ad12b2cc4be4abbfd9d96e: 19948 discards 8aca66b59 2: update: qemu-30bd1db58b09c12b68c35f041f919014b885482d: 19952 new f5e71ee96 2: update: binutils-llvm-linux-qemu: 19969
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 (b9278411e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 1788 -> 1640 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 43864 -> 44224 bytes 04-build_llvm/console.log.xz | Bin 59068 -> 59456 bytes 05-build_abe-qemu/console.log.xz | Bin 31716 -> 29788 bytes 06-build_linux/console.log.xz | Bin 8252 -> 6720 bytes 08-check_regression/console.log.xz | Bin 484 -> 484 bytes 09-update_baseline/console.log | 219 ++++++++++++++++++++++++----------- jenkins/manifest.sh | 21 ++-- results | 2 +- 10 files changed, 165 insertions(+), 77 deletions(-)