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-release-arm-next-defconfig
in repository toolchain/ci/binutils-gdb.
from b110bd43da Automatic date update in version.in
adds 135b09fbfb Automatic date update in version.in
adds 18e8fb6965 Automatic date update in version.in
adds 606ada8510 Automatic date update in version.in
adds be52d32160 Automatic date update in version.in
adds f9b660d1d6 Automatic date update in version.in
adds e2d90f8c8d Automatic date update in version.in
adds 806da170bc Automatic date update in version.in
adds 62c7851044 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_kernel/llvm-release-arm-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 182ea460 0: update: binutils-llvm-linux-qemu: boot
new 148342e1 0: update: binutils-llvm-linux-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 (182ea460)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-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 1696 -> 1556 bytes
02-prepare_abe/console.log.xz | Bin 2752 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 30364 -> 29664 bytes
04-build_llvm/console.log.xz | Bin 58416 -> 59328 bytes
05-build_abe-qemu/console.log.xz | Bin 30012 -> 31632 bytes
06-build_linux/console.log.xz | Bin 3660 -> 3468 bytes
07-boot_linux/console.log.xz | Bin 7576 -> 5968 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 18 +++++++++---------
jenkins/manifest.sh | 22 +++++++++++-----------
results | 2 +-
11 files changed, 21 insertions(+), 21 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_gnu_native_check_gcc/master-aarch64
in repository toolchain/ci/base-artifacts.
discards a6299319 0: update: gcc-1ceddd7497e15d262ead6f673f8f5ce79dd63714: 1
new a5f7a9f9 0: update: gdb-7642f36b93c08a6ca33e1399fa87a381a49749a3: 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 (a6299319)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 -> 1712 bytes
02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes
03-build_abe-binutils/console.log.xz | Bin 37456 -> 36772 bytes
04-build_abe-gcc/console.log.xz | Bin 208120 -> 208368 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 10932 -> 10540 bytes
07-build_abe-glibc/console.log.xz | Bin 235260 -> 235340 bytes
08-build_abe-gdb/console.log.xz | Bin 34820 -> 37364 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3824 bytes
10-build_abe-check_gcc/console.log.xz | Bin 3412 -> 3392 bytes
11-check_regression/console.log.xz | Bin 4388 -> 3072 bytes
11-check_regression/extra-bisect-params | 2 +-
11-check_regression/fails.sum | 11 +-
11-check_regression/results.compare | 43 +-
11-check_regression/results.compare2 | 208 +-
11-check_regression/results.regressions | 43 +-
12-update_baseline/console.log | 519 ++--
12-update_baseline/extra-bisect-params | 2 +-
12-update_baseline/fails.sum | 11 +-
12-update_baseline/results.compare | 43 +-
12-update_baseline/results.compare2 | 208 +-
12-update_baseline/results.regressions | 43 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 3673880 -> 3617480 bytes
sumfiles/g++.sum | 110 +-
sumfiles/gcc.log.xz | Bin 3168780 -> 3173060 bytes
sumfiles/gcc.sum | 4556 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 1072324 -> 1063512 bytes
sumfiles/gfortran.sum | 46 +-
sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 214396 -> 213352 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2676 -> 2672 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 429460 -> 429448 bytes
sumfiles/libstdc++.sum | 10 +-
37 files changed, 2670 insertions(+), 3219 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_gnu_cross_build/master-arm
in repository toolchain/ci/base-artifacts.
discards c4676b2f 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new 3adb0ff2 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
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 (c4676b2f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1720 -> 1536 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes
04-build_abe-binutils/console.log.xz | Bin 30124 -> 29888 bytes
05-build_abe-stage1/console.log.xz | Bin 90456 -> 91020 bytes
07-build_abe-linux/console.log.xz | Bin 9260 -> 9396 bytes
08-build_abe-glibc/console.log.xz | Bin 232456 -> 232368 bytes
09-build_abe-stage2/console.log.xz | Bin 222112 -> 221400 bytes
10-build_abe-gdb/console.log.xz | Bin 37308 -> 37172 bytes
11-build_abe-qemu/console.log.xz | Bin 31788 -> 32224 bytes
12-check_regression/console.log.xz | Bin 432 -> 416 bytes
13-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 8 ++++----
12 files changed, 5 insertions(+), 5 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.