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_binutils/master-aarch64
in repository toolchain/ci/base-artifacts.
discards c22e85f7e 0: update: binutils-gcc-linux-glibc-gdb: 1
new 6703e741f 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 (c22e85f7e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 1520 -> 1692 bytes
02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes
03-build_abe-binutils/console.log.xz | Bin 37728 -> 37632 bytes
04-build_abe-gcc/console.log.xz | Bin 208044 -> 208640 bytes
05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes
06-build_abe-linux/console.log.xz | Bin 9436 -> 9536 bytes
07-build_abe-glibc/console.log.xz | Bin 236432 -> 235936 bytes
08-build_abe-gdb/console.log.xz | Bin 37112 -> 37592 bytes
09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3872 bytes
10-build_abe-check_binutils/console.log.xz | Bin 2052 -> 2052 bytes
11-check_regression/console.log.xz | Bin 2288 -> 2288 bytes
11-check_regression/results.compare | 8 +-
11-check_regression/results.compare2 | 6 +-
12-update_baseline/console.log | 122 +++++------
12-update_baseline/results.compare | 8 +-
12-update_baseline/results.compare2 | 6 +-
jenkins/manifest.sh | 22 +-
sumfiles/binutils.log.xz | Bin 54984 -> 55020 bytes
sumfiles/binutils.sum | 58 ++---
sumfiles/gas.log.xz | Bin 80392 -> 80396 bytes
sumfiles/gas.sum | 270 +++++++++++------------
sumfiles/ld.log.xz | Bin 118320 -> 118340 bytes
sumfiles/ld.sum | 334 ++++++++++++++---------------
23 files changed, 417 insertions(+), 417 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 9b5c4fa02 0: update: binutils-gcc-linux-qemu: boot
new 75afd2405 0: update: binutils-gcc-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 (9b5c4fa02)
\
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 1588 -> 1568 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes
03-build_abe-binutils/console.log.xz | Bin 29848 -> 29956 bytes
04-build_abe-stage1/console.log.xz | Bin 90044 -> 89856 bytes
05-build_abe-qemu/console.log.xz | Bin 30552 -> 30200 bytes
06-build_linux/console.log.xz | Bin 4756 -> 4660 bytes
07-boot_linux/console.log.xz | Bin 5948 -> 5944 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 2 +-
jenkins/manifest.sh | 22 +++++++++++-----------
10 files changed, 12 insertions(+), 12 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_check_gcc/master-arm
in repository toolchain/ci/glibc.
from af6dc56b8c Guard tst-valgrind-smoke.out with run-built-tests
adds 501246c5e2 x86: Use CHECK_FEATURE_PRESENT to check HLE [BZ #27398]
No new revisions were added by this update.
Summary of changes:
sysdeps/x86/tst-cpu-features-supports.c | 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_cross_check_gcc/master-arm
in repository toolchain/ci/base-artifacts.
discards bd63c4424 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1
new 0f8404182 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (bd63c4424)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/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 1552 -> 1560 bytes
02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes
03-build_abe-binutils/console.log.xz | Bin 30420 -> 30040 bytes
04-build_abe-stage1/console.log.xz | Bin 90200 -> 90496 bytes
05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes
06-build_abe-linux/console.log.xz | Bin 9944 -> 9720 bytes
07-build_abe-glibc/console.log.xz | Bin 232360 -> 232624 bytes
08-build_abe-stage2/console.log.xz | Bin 221104 -> 221572 bytes
09-build_abe-gdb/console.log.xz | Bin 37188 -> 36972 bytes
10-build_abe-qemu/console.log.xz | Bin 30172 -> 30072 bytes
11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3856 bytes
12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2456 bytes
13-check_regression/console.log.xz | Bin 2824 -> 2404 bytes
13-check_regression/results.compare | 24 +-
13-check_regression/results.compare2 | 49 +-
14-update_baseline/console.log | 258 ++--
14-update_baseline/results.compare | 24 +-
14-update_baseline/results.compare2 | 49 +-
jenkins/manifest.sh | 8 +-
sumfiles/g++.log.xz | Bin 2598984 -> 2606756 bytes
sumfiles/g++.sum | 102 +-
sumfiles/gcc.log.xz | Bin 2132488 -> 2168008 bytes
sumfiles/gcc.sum | 2490 ++++++++++++++++-----------------
sumfiles/gfortran.log.xz | Bin 863052 -> 864604 bytes
sumfiles/gfortran.sum | 42 +-
sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 184340 -> 184348 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 416848 -> 414196 bytes
sumfiles/libstdc++.sum | 10 +-
33 files changed, 1488 insertions(+), 1594 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.