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-allyesconfig in repository toolchain/ci/base-artifacts.
discards 9d5349d7a 4: update: binutils-gcc-linux-qemu: 19307 new f3c0a0602 4: update: binutils-gcc-linux-qemu: 19307
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 (9d5349d7a) \ 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 1612 -> 1564 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 42368 -> 42480 bytes 04-build_abe-stage1/console.log.xz | Bin 90648 -> 90796 bytes 05-build_abe-qemu/console.log.xz | Bin 30392 -> 30196 bytes 06-build_linux/console.log.xz | Bin 42224 -> 42284 bytes 08-check_regression/console.log.xz | Bin 548 -> 476 bytes 08-check_regression/results.regressions | 2 - 09-update_baseline/console.log | 162 ++++++++++++++++---------------- jenkins/manifest.sh | 22 ++--- 10 files changed, 90 insertions(+), 96 deletions(-) delete mode 100644 08-check_regression/results.regressions