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-release-arm-lts-allmodconfig in repository toolchain/ci/base-artifacts.
discards e543cd17c 5: update: binutils-gcc-linux-qemu: 21793 discards 9cd2594e5 4: reset: linux-caba66ec322e22a65c388ae81b23942c7f51f982: 21793 discards 1f83e5672 3: update: binutils-gcc-qemu: 21794 new b20130105 3: update: binutils-gcc-linux-qemu: 21795
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 (e543cd17c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 1556 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 30136 bytes 04-build_abe-stage1/console.log.xz | Bin 85892 -> 86240 bytes 05-build_abe-qemu/console.log.xz | Bin 32316 -> 31952 bytes 06-build_linux/console.log.xz | Bin 5592 -> 5208 bytes 08-check_regression/console.log.xz | Bin 480 -> 480 bytes 09-update_baseline/console.log | 197 +++++++++++++++++++++++++---------- jenkins/manifest.sh | 22 ++-- results | 2 +- 10 files changed, 155 insertions(+), 66 deletions(-)