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_build/master-arm
in repository toolchain/ci/binutils-gdb.
from f9ebf60b6f Automatic date update in version.in
adds 8457023a80 Automatic date update in version.in
adds 0a9ea024e7 ld: Adjust pr28158.rd for glibc 2.34
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
ld/testsuite/ld-elf/pr28158.rd | 2 +-
2 files changed, 2 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_gnu_native_build/master-arm
in repository toolchain/ci/base-artifacts.
discards 21a48b16 0: update: binutils-gcc-linux-glibc-gdb: 6
new a56dd63e 0: update: binutils-gcc-linux-glibc-gdb: 6
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 (21a48b16)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 1544 -> 1540 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes
04-build_abe-binutils/console.log.xz | Bin 65908 -> 64880 bytes
05-build_abe-gcc/console.log.xz | Bin 231848 -> 232092 bytes
06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
07-build_abe-linux/console.log.xz | Bin 8732 -> 8916 bytes
08-build_abe-glibc/console.log.xz | Bin 227996 -> 227248 bytes
09-build_abe-gdb/console.log.xz | Bin 53604 -> 53840 bytes
10-check_regression/console.log.xz | Bin 416 -> 416 bytes
11-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 20 ++++++++++----------
11 files changed, 18 insertions(+), 18 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_check/master-arm
in repository toolchain/ci/binutils-gdb.
from f9ebf60b6f Automatic date update in version.in
adds 8457023a80 Automatic date update in version.in
adds 0a9ea024e7 ld: Adjust pr28158.rd for glibc 2.34
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
ld/testsuite/ld-elf/pr28158.rd | 2 +-
2 files changed, 2 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_gcc_check/master-arm
in repository toolchain/ci/base-artifacts.
discards b0202beb 0: update: binutils-gcc: 1
new 96075436 0: update: binutils-gcc: 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 (b0202beb)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (96075436)
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 1488 -> 1516 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 65516 -> 64724 bytes
04-build_abe-gcc/console.log.xz | Bin 232428 -> 232612 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3820 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2416 bytes
07-check_regression/console.log.xz | Bin 3072 -> 3260 bytes
07-check_regression/extra-bisect-params | 2 +-
07-check_regression/fails.sum | 11 +-
07-check_regression/results.compare | 30 +-
07-check_regression/results.compare2 | 86 +-
07-check_regression/results.regressions | 30 +-
08-update_baseline/console.log | 302 +--
08-update_baseline/extra-bisect-params | 2 +-
08-update_baseline/fails.sum | 11 +-
08-update_baseline/results.compare | 30 +-
08-update_baseline/results.compare2 | 86 +-
08-update_baseline/results.regressions | 30 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2707668 -> 2683596 bytes
sumfiles/g++.sum | 158 +-
sumfiles/gcc.log.xz | Bin 2249560 -> 2224352 bytes
sumfiles/gcc.sum | 3436 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 867992 -> 862472 bytes
sumfiles/gfortran.sum | 108 +-
sumfiles/libatomic.log.xz | Bin 2156 -> 2148 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 169156 -> 169236 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2512 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 445824 -> 450664 bytes
sumfiles/libstdc++.sum | 16 +-
33 files changed, 2233 insertions(+), 2143 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.