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-stable-allyesconfig
in repository toolchain/ci/binutils-gdb.
from 63e5eea234 [GOLD] PPC64_OPT_LOCALENTRY is incompatible with tail calls
adds 8f9929bb97 gdb: Fix from_tty argument to gdb.execute in Python.
adds 31f327a6c8 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/ChangeLog | 8 ++++++++
gdb/cli/cli-script.c | 9 +++++----
gdb/testsuite/ChangeLog | 6 ++++++
gdb/testsuite/gdb.python/python.exp | 13 +++++++++++++
5 files changed, 33 insertions(+), 5 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/gnu-master-arm-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5b077ff0c 4: update: binutils-gcc-linux: 18077
new ce0c8ebad 4: update: binutils-gcc-linux: 18077
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 (5b077ff0c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-st [...]
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 | 191 +-
02-prepare_abe/console.log | 216 +-
03-build_abe-binutils/console.log | 11564 +++++----
04-build_abe-stage1/console.log | 20016 +++++++--------
05-build_linux/console.log | 6928 +++---
07-check_regression/console.log | 12 +-
07-check_regression/results.regressions | 8 +-
08-update_baseline/console.log | 86 +-
08-update_baseline/results.regressions | 8 +-
console.log | 39013 +++++++++++++++---------------
jenkins/manifest.sh | 16 +-
11 files changed, 39078 insertions(+), 38980 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_cross/gnu-release-aarch64-check_cross
in repository toolchain/ci/base-artifacts.
discards 75f98124c 0: update: qemu-99c5874a9b6c9f70aef285d6eff85d4f46de3c52: 1
new 51ea76977 0: update: binutils-gcc-glibc-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 (75f98124c)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-release-aarch6 [...]
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 | 183 +-
02-prepare_abe/console.log | 436 +-
03-build_abe-binutils/console.log | 11257 +--
04-build_abe-stage1/console.log | 12882 +--
05-build_abe-linux/console.log | 312 +-
06-build_abe-glibc/console.log | 36383 ++++----
07-build_abe-stage2/console.log | 40353 ++++-----
08-build_abe-qemu/console.log | 2554 +-
09-build_abe-dejagnu/console.log | 336 +-
10-build_abe-check_gcc/console.log | 29161 +++---
11-check_regression/console.log | 72 +-
11-check_regression/results.regressions | 43 +-
12-update_baseline/console.log | 172 +-
12-update_baseline/results.regressions | 43 +-
console.log | 138837 ++++++++++++++---------------
jenkins/manifest.sh | 16 +-
sumfiles/g++.log.xz | Bin 1754484 -> 1761632 bytes
sumfiles/g++.sum | 70 +-
sumfiles/gcc.log.xz | Bin 1813860 -> 1796560 bytes
sumfiles/gcc.sum | 302 +-
sumfiles/gfortran.log.xz | Bin 733436 -> 735012 bytes
sumfiles/gfortran.sum | 28 +-
sumfiles/libatomic.log.xz | Bin 2064 -> 2064 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 101708 -> 101680 bytes
sumfiles/libgomp.sum | 18 +-
sumfiles/libitm.log.xz | Bin 2348 -> 2348 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 352028 -> 351756 bytes
sumfiles/libstdc++.sum | 19 +-
30 files changed, 134823 insertions(+), 138664 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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards cb285b4c7 0: update: llvm-linux: all
new decc96754 0: update: llvm-linux: all
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 (cb285b4c7)
\
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 | 14 +-
02-build_llvm/console.log | 12616 ++++++++++++++++++------------------
03-build_linux/console.log | 648 +-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 10 +-
console.log | 13292 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 13296 insertions(+), 13296 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/gnu-release-aarch64-mainline-allmodconfig
in repository toolchain/ci/gcc.
from f9b2251d584 Daily bump.
adds b61572eaf18 Daily bump.
No new revisions were added by this update.
Summary of changes:
gcc/DATESTAMP | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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/gnu-release-aarch64-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards c960e4cbc 0: update: binutils-gcc-linux: boot
new cd466bde1 0: update: binutils-gcc-linux: 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 (c960e4cbc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 | 128 +-
02-prepare_abe/console.log | 260 +-
03-build_abe-binutils/console.log | 10906 ++++++-------
04-build_abe-stage1/console.log | 13428 ++++++++--------
05-build_linux/console.log | 574 +-
06-boot_linux/console.log | 4 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 12 +-
08-update_baseline/results.regressions | 2 +-
console.log | 25318 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 25320 insertions(+), 25328 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.