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-arm-next-defconfig
in repository toolchain/ci/binutils-gdb.
from 907a9b092a Automatic date update in version.in
adds 72a6a32099 Automatic date update in version.in
adds 2de7516720 Automatic date update in version.in
adds 06ef3111fd Automatic date update in version.in
adds 158dafe913 Automatic date update in version.in
adds fb4d148004 IBM zSystems: Add support for z16 as CPU name.
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gas/config/tc-s390.c | 2 +-
gas/doc/as.texi | 4 ++--
gas/doc/c-s390.texi | 4 ++--
opcodes/s390-mkopc.c | 3 ++-
5 files changed, 8 insertions(+), 7 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-arm-next-defconfig
in repository toolchain/ci/base-artifacts.
discards d0d00b55 0: update: binutils-llvm-linux-qemu: boot
new 9f169fbd 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 (d0d00b55)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 1588 -> 1584 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 29884 -> 30404 bytes
04-build_llvm/console.log.xz | Bin 59428 -> 60968 bytes
05-build_abe-qemu/console.log.xz | Bin 30972 -> 30420 bytes
06-build_linux/console.log.xz | Bin 3508 -> 3516 bytes
07-boot_linux/console.log.xz | Bin 5960 -> 6012 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 22 +++++++++++-----------
results | 2 +-
11 files changed, 20 insertions(+), 20 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-master-arm-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards c24f0ef4 0: update: binutils-llvm-linux-qemu: boot
new ab3cfba7 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 (c24f0ef4)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 1844 -> 1600 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 32048 -> 30768 bytes
04-build_llvm/console.log.xz | Bin 61888 -> 61864 bytes
05-build_abe-qemu/console.log.xz | Bin 30788 -> 30520 bytes
06-build_linux/console.log.xz | Bin 3740 -> 4060 bytes
07-boot_linux/console.log.xz | Bin 5996 -> 6012 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 62 +++++++++++++++++------------------
jenkins/manifest.sh | 18 +++++-----
10 files changed, 40 insertions(+), 40 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_gcc_bootstrap/master-aarch64-bootstrap_O3
in repository toolchain/ci/base-artifacts.
discards 3f40ccd4 2: update: binutils-gcc: 0
new 599f35f8 2: update: binutils-gcc: 0
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 (3f40ccd4)
\
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 -> 1544 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes
04-build_abe-binutils/console.log.xz | Bin 24452 -> 21400 bytes
06-check_regression/console.log.xz | Bin 412 -> 412 bytes
07-update_baseline/console.log | 46 +++++++++++++++++------------------
jenkins/manifest.sh | 12 ++++-----
6 files changed, 29 insertions(+), 29 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_native_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 588f9b85 0: update: glibc-a085346267a368d8e802acd86ed9a9b7aee9b83d: 1
new 15b3a060 0: update: linux-42e7a03d3badebd4e70aea5362d6914dfc7c220b: 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 (588f9b85)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1536 -> 1496 bytes
02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes
03-build_abe-binutils/console.log.xz | Bin 36552 -> 36752 bytes
04-build_abe-gcc/console.log.xz | Bin 208756 -> 208588 bytes
06-build_abe-linux/console.log.xz | Bin 10684 -> 9044 bytes
07-build_abe-glibc/console.log.xz | Bin 236640 -> 235676 bytes
08-build_abe-gdb/console.log.xz | Bin 34764 -> 34696 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3828 bytes
10-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2660 bytes
11-check_regression/console.log.xz | Bin 3492 -> 3180 bytes
11-check_regression/extra-bisect-params | 2 +-
11-check_regression/fails.sum | 7 +-
11-check_regression/results.compare | 22 +-
11-check_regression/results.compare2 | 54 +-
11-check_regression/results.regressions | 22 +-
12-update_baseline/console.log | 344 ++-
12-update_baseline/extra-bisect-params | 2 +-
12-update_baseline/fails.sum | 7 +-
12-update_baseline/results.compare | 22 +-
12-update_baseline/results.compare2 | 54 +-
12-update_baseline/results.regressions | 22 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3672196 -> 3659428 bytes
sumfiles/g++.sum | 34 +-
sumfiles/gcc.log.xz | Bin 3179300 -> 3166312 bytes
sumfiles/gcc.sum | 4134 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1058592 -> 1061248 bytes
sumfiles/gfortran.sum | 54 +-
sumfiles/libatomic.log.xz | Bin 2280 -> 2272 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 214328 -> 214196 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 432796 -> 431812 bytes
sumfiles/libstdc++.sum | 4 +-
36 files changed, 2339 insertions(+), 2459 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.