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_bootstrap/master-arm-check_bootstrap
in repository toolchain/ci/binutils-gdb.
from 4c70437ddc Automatic date update in version.in
adds 561e83f7c5 Automatic date update in version.in
adds c444385fad gdb/testsuite: rename get_maint_bp_addr and move it to gdb-u [...]
adds ea892bdc4b gdb/testsuite: add a clear test to py-breakpoint.exp
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
gdb/testsuite/gdb.base/clear_non_user_bp.exp | 25 +------------------------
gdb/testsuite/gdb.python/py-breakpoint.exp | 20 ++++++++++++++++++++
gdb/testsuite/lib/gdb-utils.exp | 28 ++++++++++++++++++++++++++++
4 files changed, 50 insertions(+), 25 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_bootstrap/master-arm-check_bootstrap
in repository toolchain/ci/base-artifacts.
discards 0ebf7802 0: update: binutils-gcc: 1
new fd033e07 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 (0ebf7802)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check_bootstrap/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 1648 -> 1636 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes
03-build_abe-binutils/console.log.xz | Bin 51716 -> 51440 bytes
04-build_abe-bootstrap/console.log.xz | Bin 467864 -> 463708 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3816 bytes
06-build_abe-check_bootstrap/console.log.xz | Bin 2348 -> 2356 bytes
07-check_regression/console.log.xz | Bin 6616 -> 3188 bytes
07-check_regression/extra-bisect-params | 1 +
07-check_regression/fails.sum | 7 +
07-check_regression/results.compare | 363 +--
07-check_regression/results.compare2 | 595 +---
07-check_regression/results.regressions | 27 +
08-update_baseline/console.log | 1177 ++------
08-update_baseline/extra-bisect-params | 1 +
08-update_baseline/fails.sum | 7 +
08-update_baseline/results.compare | 363 +--
08-update_baseline/results.compare2 | 595 +---
08-update_baseline/results.regressions | 27 +
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2830204 -> 2833440 bytes
sumfiles/g++.sum | 162 +-
sumfiles/gcc.log.xz | Bin 2517372 -> 2508788 bytes
sumfiles/gcc.sum | 3981 ++++++++++++++-------------
sumfiles/gfortran.log.xz | Bin 946220 -> 942184 bytes
sumfiles/gfortran.sum | 40 +-
sumfiles/libatomic.log.xz | Bin 2300 -> 2308 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 209364 -> 208884 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 470248 -> 470580 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 2632 insertions(+), 4762 deletions(-)
create mode 100644 07-check_regression/extra-bisect-params
create mode 100644 07-check_regression/fails.sum
create mode 100644 07-check_regression/results.regressions
create mode 100644 08-update_baseline/extra-bisect-params
create mode 100644 08-update_baseline/fails.sum
create mode 100644 08-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_kernel/gnu-release-aarch64-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards df6e22c3 0: update: linux-854f56f099c9a10799554ae46f44f389d68cdb8b: boot
new bedd8b07 0: update: binutils-gcc-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 (df6e22c3)
\
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 1688 -> 1628 bytes
02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes
03-build_abe-binutils/console.log.xz | Bin 29728 -> 30544 bytes
04-build_abe-stage1/console.log.xz | Bin 69808 -> 68264 bytes
05-build_abe-qemu/console.log.xz | Bin 33472 -> 30608 bytes
06-build_linux/console.log.xz | Bin 3332 -> 5548 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 | 10 +++++-----
jenkins/manifest.sh | 18 ++++++++++--------
10 files changed, 15 insertions(+), 13 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.