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-lts-allyesconfig in repository toolchain/ci/base-artifacts.
discards 9a7903b1 4: update: binutils-llvm-linux-qemu: 18849 discards 6f945bc5 3: reset: llvm-35737df4dcd28534bd3090157c224c19b501278a: 18848 discards f829e2f4 2: update: qemu-aeb0ae95b7f18c66158792641cb6ba0cde5789ab: 19900 new 16da41ef 2: update: binutils-llvm-linux-qemu: 19902
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 (9a7903b1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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 1572 -> 1560 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30580 bytes 04-build_llvm/console.log.xz | Bin 60120 -> 61432 bytes 05-build_abe-qemu/console.log.xz | Bin 30968 -> 30800 bytes 06-build_linux/console.log.xz | Bin 41412 -> 5156 bytes 08-check_regression/console.log.xz | Bin 480 -> 484 bytes 09-update_baseline/console.log | 322 ++++++++++++++++++++++------------- jenkins/manifest.sh | 22 +-- results | 2 +- 10 files changed, 218 insertions(+), 128 deletions(-)