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-mainline-allyesconfig in repository toolchain/ci/base-artifacts.
discards def334296 2: update: gcc-57fdcaf17d4b5b9dc4bb72840f882d2e7e6294ef: 20581 new 6c0132f9f 2: update: binutils-gcc-linux-qemu: 20628
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 (def334296) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 1620 -> 1612 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 29192 -> 29864 bytes 04-build_abe-stage1/console.log.xz | Bin 86032 -> 86152 bytes 05-build_abe-qemu/console.log.xz | Bin 32568 -> 31884 bytes 06-build_linux/console.log.xz | Bin 14908 -> 12116 bytes 08-check_regression/console.log.xz | Bin 484 -> 484 bytes 09-update_baseline/console.log | 111 ++++++++++++++++++++++++----------- jenkins/manifest.sh | 21 ++++--- results | 2 +- 10 files changed, 90 insertions(+), 44 deletions(-)