This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_O3
in repository toolchain/ci/base-artifacts.
discards c4a897ff0 2: update: binutils-b243230f64fb4db9a16ef88ec5bd3e3f48f1fe41: 0
discards 30bb876df 1: reset: binutils-fe72c32765e1190c8a17d309fc3a7e1882d6a430: 0
discards f9b4b2a1d 0: update: gcc-f157c5362b4844f7676cae2aba81a4cf75bd68d5: 2
new b49d66e54 0: update: binutils-gcc: 2
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 (c4a897ff0)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 -> 1564 bytes
02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes
04-build_abe-binutils/console.log.xz | Bin 32952 -> 38804 bytes
05-build_abe-bootstrap_O3/console.log.xz | Bin 0 -> 264884 bytes
06-check_regression/console.log.xz | Bin 412 -> 416 bytes
07-update_baseline/console.log | 90 +++++++++++++++++++------------
07-update_baseline/results.regressions | 2 -
jenkins/manifest.sh | 12 +++--
results | 4 ++
9 files changed, 68 insertions(+), 40 deletions(-)
create mode 100644 05-build_abe-bootstrap_O3/console.log.xz
delete mode 100644 07-update_baseline/results.regressions
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards b66ce09a3 0: update: binutils-llvm-linux-qemu: boot
new 4cfba8e84 0: update: binutils-llvm-linux-qemu: boot
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 (b66ce09a3)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 1552 -> 1548 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 30904 -> 31128 bytes
04-build_llvm/console.log.xz | Bin 58372 -> 58856 bytes
05-build_abe-qemu/console.log.xz | Bin 29088 -> 29984 bytes
06-build_linux/console.log.xz | Bin 3780 -> 3784 bytes
07-boot_linux/console.log.xz | Bin 5792 -> 5784 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 10 +++++-----
jenkins/manifest.sh | 20 ++++++++++----------
10 files changed, 15 insertions(+), 15 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.