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 914e8a3e 0: update: binutils-gcc: 1
new ef67d12c 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 (914e8a3e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (ef67d12c)
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 1480 -> 1516 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes
03-build_abe-binutils/console.log.xz | Bin 51680 -> 52144 bytes
04-build_abe-gcc/console.log.xz | Bin 229116 -> 229040 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3828 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2572 -> 3272 bytes
07-check_regression/console.log.xz | Bin 2340 -> 2488 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 19 +-
08-update_baseline/console.log | 348 +--
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 19 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2747008 -> 2765500 bytes
sumfiles/g++.sum | 138 +-
sumfiles/gcc.log.xz | Bin 2336224 -> 2351080 bytes
sumfiles/gcc.sum | 4456 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 897688 -> 900120 bytes
sumfiles/gfortran.sum | 44 +-
sumfiles/libatomic.log.xz | Bin 2152 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 198632 -> 198868 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2540 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 452560 -> 458000 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2567 insertions(+), 2537 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-aarch64-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 63de4c55 2: update: linux-f9006d9269eac8ff295c2cb67280c54888c74106: 20553
new 7f8a3a97 2: update: gcc-4a3073f04e8b7987ad7bfe1bc23bfeb1d627ee6a: 20674
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 (63de4c55)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-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.xz | Bin 1740 -> 1608 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes
03-build_abe-binutils/console.log.xz | Bin 30380 -> 29420 bytes
04-build_abe-stage1/console.log.xz | Bin 73200 -> 72420 bytes
05-build_abe-qemu/console.log.xz | Bin 32848 -> 32768 bytes
06-build_linux/console.log.xz | Bin 54676 -> 19088 bytes
08-check_regression/console.log.xz | Bin 480 -> 484 bytes
09-update_baseline/console.log | 26 +++++++++++++-------------
jenkins/manifest.sh | 8 ++++----
results | 2 +-
10 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_bootstrap/release-arm-bootstrap_O3
in repository toolchain/ci/binutils-gdb.
from d30575b3e8 Automatic date update in version.in
adds 5ff8cdfa77 Automatic date update in version.in
adds 5b33ea463f Automatic date update in version.in
adds 41fb8cf201 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_gcc_bootstrap/release-arm-bootstrap_O3
in repository toolchain/ci/base-artifacts.
discards e57d3fe1 0: update: binutils-gcc: 2
new 233812ca 0: update: binutils-gcc: 2
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 (e57d3fe1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/release-ar [...]
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 1496 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes
04-build_abe-binutils/console.log.xz | Bin 48140 -> 49232 bytes
05-build_abe-bootstrap_O3/console.log.xz | Bin 451076 -> 447576 bytes
06-check_regression/console.log.xz | Bin 416 -> 416 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
7 files changed, 14 insertions(+), 14 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.
unknown user pushed a change to branch master
in repository binutils-gdb.
from 4414150d332 gdbserver: Fixup previous patch
new d37e084783a Watchpoint followed by catchpoint misreports watchpoint (PR [...]
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:
gdb/breakpoint.c | 15 ++++
gdb/breakpoint.h | 25 +++++-
gdb/infrun.c | 24 +++---
.../watch-before-fork.c} | 7 +-
gdb/testsuite/gdb.base/watch-before-fork.exp | 99 ++++++++++++++++++++++
5 files changed, 153 insertions(+), 17 deletions(-)
copy gdb/testsuite/{gdb.opt/break-on-_exit.c => gdb.base/watch-before-fork.c} (90%)
create mode 100644 gdb/testsuite/gdb.base/watch-before-fork.exp
--
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-arm-bootstrap_ubsan
in repository toolchain/ci/base-artifacts.
discards 7a299daf 0: update: binutils-gcc: 2
new b97c7dfc 0: update: binutils-gcc: 2
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 (7a299daf)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-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.xz | Bin 1536 -> 1500 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes
04-build_abe-binutils/console.log.xz | Bin 50944 -> 51284 bytes
05-build_abe-bootstrap_ubsan/console.log.xz | Bin 527900 -> 528500 bytes
06-check_regression/console.log.xz | Bin 420 -> 420 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 12 ++++++------
7 files changed, 14 insertions(+), 14 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.