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-aarch64
in repository toolchain/ci/gcc.
from af93386ffc1 [PR103097] tolerate reg-stack cross-block malformed asms
adds 5791bf7a0a7 D: fix UBSAN
No new revisions were added by this update.
Summary of changes:
gcc/d/expr.cc | 3 ++-
1 file changed, 2 insertions(+), 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_build/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 67f90138 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7
new bd0457bf 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 (67f90138)
\
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 1564 -> 1548 bytes
02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes
04-build_abe-binutils/console.log.xz | Bin 32736 -> 31148 bytes
05-build_abe-stage1/console.log.xz | Bin 71076 -> 71076 bytes
06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes
07-build_abe-linux/console.log.xz | Bin 9332 -> 9436 bytes
08-build_abe-glibc/console.log.xz | Bin 235804 -> 236880 bytes
09-build_abe-stage2/console.log.xz | Bin 194964 -> 194016 bytes
10-build_abe-gdb/console.log.xz | Bin 40228 -> 38912 bytes
11-build_abe-qemu/console.log.xz | Bin 30260 -> 29764 bytes
12-check_regression/console.log.xz | Bin 416 -> 416 bytes
13-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 22 +++++++++++-----------
13 files changed, 19 insertions(+), 19 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-release-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 8856547f 0: update: linux-58da0d84fdd2563939dafa48334e190fad1b536c: all
new dd81f46c 0: update: linux-58da0d84fdd2563939dafa48334e190fad1b536c: 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 (8856547f)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]
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 -> 1604 bytes
02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes
03-build_abe-binutils/console.log.xz | Bin 40888 -> 41192 bytes
04-build_abe-stage1/console.log.xz | Bin 86748 -> 87084 bytes
05-build_abe-qemu/console.log.xz | Bin 29196 -> 30532 bytes
06-build_linux/console.log.xz | Bin 3128 -> 3112 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 412 -> 412 bytes
09-update_baseline/console.log | 16 ++++++++--------
jenkins/manifest.sh | 4 ++--
10 files changed, 10 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-aarch64
in repository toolchain/ci/gcc.
from af93386ffc1 [PR103097] tolerate reg-stack cross-block malformed asms
adds 5791bf7a0a7 D: fix UBSAN
No new revisions were added by this update.
Summary of changes:
gcc/d/expr.cc | 3 ++-
1 file changed, 2 insertions(+), 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_check/master-aarch64
in repository toolchain/ci/base-artifacts.
discards 1fc1ba47 0: update: binutils-gcc: 1
new ccb7248e 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 (1fc1ba47)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...]
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 -> 1520 bytes
02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes
03-build_abe-binutils/console.log.xz | Bin 40896 -> 38740 bytes
04-build_abe-gcc/console.log.xz | Bin 202680 -> 202516 bytes
05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3864 bytes
06-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2532 bytes
07-check_regression/console.log.xz | Bin 3124 -> 3052 bytes
07-check_regression/fails.sum | 7 +-
07-check_regression/results.compare | 30 +-
07-check_regression/results.compare2 | 46 +-
07-check_regression/results.regressions | 30 +-
08-update_baseline/console.log | 480 ++--
08-update_baseline/fails.sum | 7 +-
08-update_baseline/results.compare | 30 +-
08-update_baseline/results.compare2 | 46 +-
08-update_baseline/results.regressions | 30 +-
jenkins/manifest.sh | 12 +-
sumfiles/g++.log.xz | Bin 3449728 -> 3475020 bytes
sumfiles/g++.sum | 116 +-
sumfiles/gcc.log.xz | Bin 2937212 -> 2959164 bytes
sumfiles/gcc.sum | 4696 +++++++++++++++----------------
sumfiles/gfortran.log.xz | Bin 882344 -> 877352 bytes
sumfiles/gfortran.sum | 44 +-
sumfiles/libatomic.log.xz | Bin 2168 -> 2168 bytes
sumfiles/libatomic.sum | 4 +-
sumfiles/libgomp.log.xz | Bin 175860 -> 175956 bytes
sumfiles/libgomp.sum | 16 +-
sumfiles/libitm.log.xz | Bin 2536 -> 2532 bytes
sumfiles/libitm.sum | 6 +-
sumfiles/libstdc++.log.xz | Bin 426700 -> 430652 bytes
sumfiles/libstdc++.sum | 10 +-
31 files changed, 2780 insertions(+), 2830 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.