This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_fx/gnu-master-aarch64-cpu2017-O2 in repository toolchain/ci/base-artifacts.
discards c862a3d4 0: init: binutils-gcc-linux-glibc: 1 new f372e5bf 0: init: binutils-gcc-linux-glibc: 1
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 (c862a3d4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_gnu_fx/gnu-master-aa [...]
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 1484 -> 1520 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30760 -> 31044 bytes 04-build_abe-stage1/console.log.xz | Bin 73904 -> 74096 bytes 06-build_abe-linux/console.log.xz | Bin 9140 -> 9120 bytes 07-build_abe-glibc/console.log.xz | Bin 239960 -> 240320 bytes 08-build_abe-stage2/console.log.xz | Bin 182192 -> 184676 bytes 09-benchmark/benchmark-build.log | 32 ++++++++++++++++---------------- 09-benchmark/benchmark.log | 30 +++++++++++++++--------------- 09-benchmark/console.log.xz | Bin 3004 -> 2988 bytes 10-check_regression/console.log.xz | Bin 360 -> 360 bytes jenkins/manifest.sh | 16 ++++++++-------- results_id | 2 +- 13 files changed, 40 insertions(+), 40 deletions(-)