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-next-allmodconfig in repository toolchain/ci/base-artifacts.

discards 10837c61 4: update: gcc-4cdf7db9a39d18bd536d816a5751d4d3cf23808b: 21276 discards efb3cabc 3: reset: gcc-f98f373dd822b35c52356b753d528924e9f89678: 21276 discards d9f24245 2: update: qemu-9104bd89dadd0b17c414ba24b0841d0042179a2e: 21279 new 7e2cc56a 2: update: binutils-gcc-linux-qemu: 21305

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 (10837c61) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]

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 1540 -> 1604 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 43576 -> 44984 bytes 04-build_abe-stage1/console.log.xz | Bin 89988 -> 90464 bytes 05-build_abe-qemu/console.log.xz | Bin 31416 -> 29636 bytes 06-build_linux/console.log.xz | Bin 46236 -> 43876 bytes 08-check_regression/console.log.xz | Bin 476 -> 484 bytes 09-update_baseline/console.log | 231 ++++++++++++++++++++++++----------- jenkins/manifest.sh | 19 +-- results | 2 +- 10 files changed, 170 insertions(+), 82 deletions(-)