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_check_gdb/release-aarch64
in repository toolchain/ci/binutils-gdb.
from 957b1d8f2f Automatic date update in version.in
adds 2cbc1315ac Automatic date update in version.in
adds fc0ff94085 Automatic date update in version.in
adds aa20be8d05 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_check_gdb/release-aarch64
in repository toolchain/ci/base-artifacts.
discards ee2ee534e 0: update: binutils-gcc-linux-glibc-gdb: 1
new 05153dbc8 0: update: binutils-gcc-linux-glibc-gdb: 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 (ee2ee534e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/rel [...]
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 1552 -> 1552 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 51728 -> 51504 bytes
04-build_abe-gcc/console.log.xz | Bin 192556 -> 192180 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 8740 -> 8768 bytes
07-build_abe-glibc/console.log.xz | Bin 296608 -> 293936 bytes
08-build_abe-gdb/console.log.xz | Bin 41936 -> 41812 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3828 bytes
10-build_abe-check_gdb/console.log.xz | Bin 2012 -> 2000 bytes
11-check_regression/console.log.xz | Bin 4888 -> 4012 bytes
11-check_regression/extra-bisect-params | 2 +-
11-check_regression/fails.sum | 24 +-
11-check_regression/results.compare | 109 +-
11-check_regression/results.compare2 | 255 +-
11-check_regression/results.regressions | 102 +-
12-update_baseline/console.log | 555 ++---
12-update_baseline/extra-bisect-params | 2 +-
12-update_baseline/fails.sum | 24 +-
12-update_baseline/results.compare | 109 +-
12-update_baseline/results.compare2 | 255 +-
12-update_baseline/results.regressions | 102 +-
jenkins/manifest.sh | 18 +-
sumfiles/gdb.log.xz | Bin 1766020 -> 1742580 bytes
sumfiles/gdb.sum | 4131 ++++++++++++++++---------------
25 files changed, 2613 insertions(+), 3075 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 38dac12e2 0: update: binutils-gcc: 1
new dd8a481cc 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 (38dac12e2)
\
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 1544 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 64516 -> 64904 bytes
04-build_abe-bootstrap/console.log.xz | Bin 462772 -> 462876 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3804 bytes
06-build_abe-check_bootstrap/console.log.xz | Bin 2344 -> 2440 bytes
07-check_regression/console.log.xz | Bin 2888 -> 2384 bytes
07-check_regression/results.compare | 16 +-
07-check_regression/results.compare2 | 77 +-
08-update_baseline/console.log | 286 +-
08-update_baseline/results.compare | 16 +-
08-update_baseline/results.compare2 | 77 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 2713460 -> 2738604 bytes
sumfiles/g++.sum | 102 +-
sumfiles/gcc.log.xz | Bin 2316028 -> 2337352 bytes
sumfiles/gcc.sum | 3768 +++++++++++++--------------
sumfiles/gfortran.log.xz | Bin 905688 -> 893548 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 171852 -> 172740 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2712 -> 2708 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 456128 -> 463752 bytes
sumfiles/libstdc++.sum | 10 +-
27 files changed, 2124 insertions(+), 2308 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/llvm-master-arm-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards e3ea189a8 0: update: binutils-llvm-linux-qemu: all
new 70ca97fe8 0: update: binutils-llvm-linux-qemu: all
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 (e3ea189a8)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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 1560 -> 1568 bytes
02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 42844 -> 42180 bytes
04-build_llvm/console.log.xz | Bin 59312 -> 59128 bytes
05-build_abe-qemu/console.log.xz | Bin 30636 -> 30144 bytes
06-build_linux/console.log.xz | Bin 4148 -> 4004 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 524 -> 412 bytes
08-check_regression/results.regressions | 2 --
09-update_baseline/console.log | 13 ++++---------
09-update_baseline/results.regressions | 2 --
jenkins/manifest.sh | 22 +++++++++++-----------
12 files changed, 15 insertions(+), 24 deletions(-)
delete mode 100644 08-check_regression/results.regressions
delete mode 100644 09-update_baseline/results.regressions
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.