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-stable-allmodconfig
in repository toolchain/ci/binutils-gdb.
from 5b33ea463f Automatic date update in version.in
adds 41fb8cf201 Automatic date update in version.in
adds 8a78349beb Automatic date update in version.in
adds 26ab93fb53 Automatic date update in version.in
adds 9985236551 dlltool: Use the output name as basis for deterministic temp [...]
new 92b4ebaa2d Automatic date update in version.in
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:
bfd/version.h | 2 +-
binutils/ChangeLog | 9 +++++++++
binutils/dlltool.c | 7 ++++---
3 files changed, 14 insertions(+), 4 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-stable-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 51bccbaa 0: update: binutils-gcc-linux-qemu: boot
new 9b8c1023 0: update: binutils-gcc-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 (51bccbaa)
\
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.xz | Bin 1708 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 30280 -> 30140 bytes
04-build_abe-stage1/console.log.xz | Bin 67504 -> 67460 bytes
05-build_abe-qemu/console.log.xz | Bin 31132 -> 30388 bytes
06-build_linux/console.log.xz | Bin 3468 -> 3428 bytes
07-boot_linux/console.log.xz | Bin 508 -> 508 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 19 insertions(+), 19 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 87fd1b77 0: update: linux-6b1f86f8e9c7f9de7ca1cb987b2cf25e99b1ae3a: 1
new 1993a00b 0: update: qemu-15ef89d2a1a7b93845a6b09c2ee8e1979f6eb30b: 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 (87fd1b77)
\
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 1580 -> 1588 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2776 bytes
03-build_abe-binutils/console.log.xz | Bin 30064 -> 30220 bytes
04-build_abe-stage1/console.log.xz | Bin 72968 -> 73268 bytes
06-build_abe-linux/console.log.xz | Bin 9588 -> 11464 bytes
07-build_abe-glibc/console.log.xz | Bin 235404 -> 235448 bytes
08-build_abe-stage2/console.log.xz | Bin 199184 -> 199532 bytes
09-build_abe-gdb/console.log.xz | Bin 34260 -> 34544 bytes
10-build_abe-qemu/console.log.xz | Bin 31900 -> 30640 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3920 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 2744 bytes
13-check_regression/console.log.xz | Bin 5804 -> 9544 bytes
13-check_regression/extra-bisect-params | 1 +
13-check_regression/fails.sum | 301 ++
13-check_regression/results.compare | 323 +-
13-check_regression/results.compare2 | 2375 +++++++++----
13-check_regression/results.regressions | 101 +
14-update_baseline/console.log | 2894 ++++++++++-----
14-update_baseline/extra-bisect-params | 1 +
14-update_baseline/fails.sum | 301 ++
14-update_baseline/results.compare | 323 +-
14-update_baseline/results.compare2 | 2375 +++++++++----
14-update_baseline/results.regressions | 101 +
jenkins/manifest.sh | 6 +-
sumfiles/g++.log.xz | Bin 3339696 -> 3333136 bytes
sumfiles/g++.sum | 48 +-
sumfiles/gcc.log.xz | Bin 2924116 -> 2915696 bytes
sumfiles/gcc.sum | 5879 ++++++++++++++++---------------
sumfiles/gfortran.log.xz | Bin 1021624 -> 1018764 bytes
sumfiles/gfortran.sum | 4 +-
sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 196360 -> 196248 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2652 -> 2664 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 406328 -> 405424 bytes
sumfiles/libstdc++.sum | 8 +-
38 files changed, 9823 insertions(+), 5224 deletions(-)
create mode 100644 13-check_regression/extra-bisect-params
create mode 100644 13-check_regression/fails.sum
create mode 100644 13-check_regression/results.regressions
create mode 100644 14-update_baseline/extra-bisect-params
create mode 100644 14-update_baseline/fails.sum
create mode 100644 14-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_gcc_bootstrap/master-aarch64-bootstrap
in repository toolchain/ci/binutils-gdb.
from faf5e6ace8 libctf: add LIBCTF_WRITE_FOREIGN_ENDIAN debugging option
adds b24ae11cd4 gdb/testsuite: address test failures in gdb.mi/mi-multi-comm [...]
adds 21152986f1 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/testsuite/gdb.mi/mi-multi-commands.exp | 7 +++++--
2 files changed, 6 insertions(+), 3 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
in repository toolchain/ci/base-artifacts.
discards fe489245 2: update: binutils-gcc: 0
new f08abfa2 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 (fe489245)
\
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 1552 -> 1512 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes
04-build_abe-binutils/console.log.xz | Bin 25048 -> 24400 bytes
06-check_regression/console.log.xz | Bin 412 -> 416 bytes
07-update_baseline/console.log | 90 +++++++++++++++++------------------
jenkins/manifest.sh | 10 ++--
6 files changed, 50 insertions(+), 50 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_build/master-arm
in repository toolchain/ci/gdb.
from b24ae11cd4 gdb/testsuite: address test failures in gdb.mi/mi-multi-comm [...]
adds 21152986f1 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 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_gnu_cross_build/master-arm
in repository toolchain/ci/binutils-gdb.
from b24ae11cd4 gdb/testsuite: address test failures in gdb.mi/mi-multi-comm [...]
adds 21152986f1 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.