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/gdb.
from 0b99131d48 Automatic date update in version.in
adds 6d8b70895c 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_native_build/master-arm
in repository toolchain/ci/binutils-gdb.
from 0b99131d48 Automatic date update in version.in
adds 6d8b70895c 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_native_build/master-arm
in repository toolchain/ci/base-artifacts.
discards e554e493 0: update: binutils-gcc-linux-glibc-gdb: 6
new 34150514 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 (e554e493)
\
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 1540 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2744 bytes
04-build_abe-binutils/console.log.xz | Bin 52440 -> 52812 bytes
05-build_abe-gcc/console.log.xz | Bin 229376 -> 231932 bytes
06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes
07-build_abe-linux/console.log.xz | Bin 9524 -> 9172 bytes
08-build_abe-glibc/console.log.xz | Bin 231044 -> 232672 bytes
09-build_abe-gdb/console.log.xz | Bin 49224 -> 49956 bytes
10-check_regression/console.log.xz | Bin 416 -> 416 bytes
11-update_baseline/console.log | 36 +++++++++++++++++++++++++++++++++++
jenkins/manifest.sh | 20 +++++++++----------
11 files changed, 46 insertions(+), 10 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 2ab1b87b 0: update: binutils-gcc: 1
new d8ebd9c3 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 (2ab1b87b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (d8ebd9c3)
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 1652 -> 1516 bytes
02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes
03-build_abe-binutils/console.log.xz | Bin 51804 -> 52200 bytes
04-build_abe-gcc/console.log.xz | Bin 230272 -> 230164 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3892 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2396 -> 2900 bytes
07-check_regression/console.log.xz | Bin 2384 -> 2684 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 65 +-
08-update_baseline/console.log | 216 +-
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 65 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2768896 -> 2764716 bytes
sumfiles/g++.sum | 170 +-
sumfiles/gcc.log.xz | Bin 2326392 -> 2360696 bytes
sumfiles/gcc.sum | 4962 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 905248 -> 897004 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2172 -> 2172 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 200296 -> 200344 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 458396 -> 459916 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2867 insertions(+), 2729 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.