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 c18e6cab8 0: update: binutils-gcc: 1
new 03ae2cbee 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 (c18e6cab8)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (03 [...]
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 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2716 -> 2704 bytes
03-build_abe-binutils/console.log.xz | Bin 51044 -> 52596 bytes
04-build_abe-gcc/console.log.xz | Bin 232236 -> 232164 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3812 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2404 -> 2408 bytes
07-check_regression/console.log.xz | Bin 2760 -> 2372 bytes
07-check_regression/results.compare | 31 +-
07-check_regression/results.compare2 | 36 +-
08-update_baseline/console.log | 298 +--
08-update_baseline/results.compare | 31 +-
08-update_baseline/results.compare2 | 36 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2793612 -> 2794576 bytes
sumfiles/g++.sum | 132 +-
sumfiles/gcc.log.xz | Bin 2336548 -> 2337392 bytes
sumfiles/gcc.sum | 4356 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 899316 -> 897340 bytes
sumfiles/gfortran.sum | 44 +-
sumfiles/libatomic.log.xz | Bin 2160 -> 2160 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 201784 -> 201616 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2540 -> 2548 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 457164 -> 454788 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2450 insertions(+), 2562 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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards dcc6a1749 6: update: binutils-gcc-linux-qemu: 33
new 808426b18 6: update: binutils-gcc-linux-qemu: 33
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 (dcc6a1749)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]
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 1592 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 30028 -> 30484 bytes
04-build_abe-stage1/console.log.xz | Bin 90320 -> 90172 bytes
05-build_abe-qemu/console.log.xz | Bin 32240 -> 32872 bytes
06-build_linux/console.log.xz | Bin 5048 -> 4848 bytes
08-check_regression/console.log.xz | Bin 480 -> 476 bytes
09-update_baseline/console.log | 12 ++++++------
jenkins/manifest.sh | 22 +++++++++++-----------
9 files changed, 17 insertions(+), 17 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 db802012a3 Automatic date update in version.in
adds aef4bdb2ed Automatic date update in version.in
adds 724f6468fb Automatic date update in version.in
adds c86fbb1d88 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 b5fc64fd7 0: update: binutils-gcc: 2
new 705729ef4 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 (b5fc64fd7)
\
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 1536 -> 1532 bytes
02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes
04-build_abe-binutils/console.log.xz | Bin 48100 -> 48368 bytes
05-build_abe-bootstrap_O3/console.log.xz | Bin 452744 -> 453804 bytes
06-check_regression/console.log.xz | Bin 416 -> 420 bytes
07-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 14 +++++++-------
7 files changed, 15 insertions(+), 15 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 772f4c2e981 gdb/testsuite: add missing skip_python_tests call in py-doc [...]
new faec7017f03 [gdb] Fix maint selftest -v print_one_insn
new 4ab19f4c9b3 [gdb] Enable some more print_one_insn selftests
new 38015f6710d [gdb] Name arch selftests more clearly
The 3 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/disasm-selftests.c | 28 ++++++++++++++++++++--------
gdb/selftest-arch.c | 27 ++++++++++++++++++++++-----
2 files changed, 42 insertions(+), 13 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.