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-release-aarch64-stable-allyesconfig
in repository toolchain/ci/binutils-gdb.
from 8e001ed8f2 Automatic date update in version.in
adds eed56ee299 Automatic date update in version.in
adds 97dd8079fe PowerPC64: fix assertion in ppc_build_one_stub with -Os code
adds fa7673bf14 Automatic date update in version.in
adds faa0405980 Automatic date update in version.in
adds f1f91e76db Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/elf64-ppc.c | 3 ++-
bfd/version.h | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
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-release-aarch64-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 0f3bb173 2: update: binutils-llvm-linux-qemu: 20722
new 8ed6f30b 2: update: binutils-llvm-linux-qemu: 20722
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 (0f3bb173)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 1568 -> 1568 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 30452 -> 30424 bytes
04-build_kernel_llvm/console.log.xz | Bin 60788 -> 62800 bytes
05-build_abe-qemu/console.log.xz | Bin 33316 -> 33196 bytes
06-build_linux/console.log.xz | Bin 4532 -> 4520 bytes
08-check_regression/console.log.xz | Bin 484 -> 476 bytes
09-update_baseline/console.log | 217 ++++++++++++++++++-----------------
jenkins/manifest.sh | 18 +--
9 files changed, 118 insertions(+), 117 deletions(-)
--
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_gnu_cross_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 9c948df5 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new eaa747ca 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (9c948df5)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1548 -> 1540 bytes
02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes
03-build_abe-binutils/console.log.xz | Bin 30492 -> 30500 bytes
04-build_abe-stage1/console.log.xz | Bin 72464 -> 71908 bytes
06-build_abe-linux/console.log.xz | Bin 10188 -> 9080 bytes
07-build_abe-glibc/console.log.xz | Bin 238712 -> 238724 bytes
08-build_abe-stage2/console.log.xz | Bin 202348 -> 203152 bytes
09-build_abe-gdb/console.log.xz | Bin 37484 -> 37464 bytes
10-build_abe-qemu/console.log.xz | Bin 33004 -> 33444 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2592 -> 2688 bytes
13-check_regression/console.log.xz | Bin 14852 -> 14824 bytes
13-check_regression/extra-bisect-params | 2 +-
13-check_regression/fails.sum | 21 +-
13-check_regression/results.compare | 41 +-
13-check_regression/results.compare2 | 3164 ++++++++++-----------
13-check_regression/results.regressions | 41 +-
14-update_baseline/console.log | 3433 +++++++++++------------
14-update_baseline/extra-bisect-params | 2 +-
14-update_baseline/fails.sum | 21 +-
14-update_baseline/results.compare | 41 +-
14-update_baseline/results.compare2 | 3164 ++++++++++-----------
14-update_baseline/results.regressions | 41 +-
jenkins/manifest.sh | 14 +-
sumfiles/g++.log.xz | Bin 3367148 -> 3382132 bytes
sumfiles/g++.sum | 3117 ++++++++++-----------
sumfiles/gcc.log.xz | Bin 2960692 -> 2976720 bytes
sumfiles/gcc.sum | 4594 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 1030604 -> 1022076 bytes
sumfiles/gfortran.sum | 8 +-
sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 199060 -> 199264 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 424140 -> 418088 bytes
sumfiles/libstdc++.sum | 8 +-
38 files changed, 8747 insertions(+), 8971 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.