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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards bb750e13 0: update: binutils-gcc-linux: all
new 5161cddb 0: update: binutils-gcc-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 (bb750e13)
\
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 | 63 +-
02-prepare_abe/console.log | 414 +-
03-build_abe-binutils/console.log | 9880 ++++++------
04-build_abe-stage1/console.log | 13920 +++++++++--------
05-build_linux/console.log | 462 +-
07-check_regression/console.log | 18 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 52 +-
08-update_baseline/results.regressions | 2 +-
console.log | 24815 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
11 files changed, 24787 insertions(+), 24849 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-next-allyesconfig
in repository toolchain/ci/binutils-gdb.
from ed5e05a2cf Automatic date update in version.in
adds 8d748d1dc5 PR26907, segment contains empty SHT_NOBITS section
adds b413232211 GDB: Fix detection of ELF support when configuring with -Wer [...]
adds b214250c1e Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/ChangeLog | 6 ++++++
bfd/elf.c | 3 ++-
bfd/version.h | 2 +-
gdb/ChangeLog | 5 +++++
gdb/acinclude.m4 | 1 +
gdb/configure | 2 ++
ld/ChangeLog | 6 ++++++
ld/testsuite/ld-elf/pr26907.d | 9 +++++++++
ld/testsuite/ld-elf/{header.t => pr26907.ld} | 5 ++---
ld/testsuite/ld-elf/pr26907.s | 9 +++++++++
10 files changed, 43 insertions(+), 5 deletions(-)
create mode 100644 ld/testsuite/ld-elf/pr26907.d
copy ld/testsuite/ld-elf/{header.t => pr26907.ld} (57%)
create mode 100644 ld/testsuite/ld-elf/pr26907.s
--
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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c2301900 2: update: binutils-gcc-linux: 19261
new 0e90630b 2: update: binutils-gcc-linux: 19261
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 (c2301900)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
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 | 193 +-
02-prepare_abe/console.log | 446 +-
03-build_abe-binutils/console.log | 11436 +++++-----
04-build_abe-stage1/console.log | 20080 ++++++++---------
05-build_linux/console.log | 2188 +-
07-check_regression/console.log | 18 +-
07-check_regression/results.regressions | 20 +-
08-update_baseline/console.log | 105 +-
08-update_baseline/results.regressions | 20 +-
console.log | 34716 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
11 files changed, 34541 insertions(+), 34693 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-master-arm-check_cross
in repository toolchain/ci/base-artifacts.
discards 4ef20db4 7: update: glibc-9ff2674ef82eccd5ae5dfa6bb733c0e3613764c6: 1
discards 5654e5c5 6: reset: qemu-1b539bd6dbe1459f160e25610ec2fc3388f700e8: 1
new 8608eff9 6: reset: qemu-8e242b3cb4cb9f7c2eeeec12a79d99a12c8e0ecf: 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 (4ef20db4)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-master-arm-che [...]
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 | 237 +-
02-prepare_abe/console.log | 436 +-
03-build_abe-binutils/console.log | 10524 +-
04-build_abe-stage1/console.log | 19844 ++--
05-build_abe-linux/console.log | 296 +-
06-build_abe-glibc/console.log | 39701 ++++---
07-build_abe-stage2/console.log | 46756 ++++----
08-build_abe-qemu/console.log | 3348 +-
09-build_abe-dejagnu/console.log | 294 +-
10-build_abe-check_gcc/console.log | 31038 +++---
11-check_regression/console.log | 328 +-
11-check_regression/results.regressions | 6 +-
12-update_baseline/console.log | 15659 ++-
12-update_baseline/results.regressions | 6 +-
console.log | 168507 ++++++++++++++---------------
jenkins/manifest.sh | 12 +-
reset-baseline | 0
sumfiles/g++.log.xz | Bin 2289008 -> 2298912 bytes
sumfiles/g++.sum | 92 +-
sumfiles/gcc.log.xz | Bin 2017068 -> 1990496 bytes
sumfiles/gcc.sum | 312 +-
sumfiles/gfortran.log.xz | Bin 769076 -> 768272 bytes
sumfiles/gfortran.sum | 32 +-
sumfiles/libatomic.log.xz | Bin 2228 -> 2232 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 127164 -> 127268 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2604 -> 2600 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 412256 -> 413196 bytes
sumfiles/libstdc++.sum | 8 +-
31 files changed, 165194 insertions(+), 172268 deletions(-)
create mode 100644 reset-baseline
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.