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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 662ab2af 0: update: binutils-gcc-linux-qemu: boot
new aaeb9e36 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 (662ab2af)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 102 +-
02-prepare_abe/console.log | 140 +-
03-build_abe-binutils/console.log | 11479 +++++-----
04-build_abe-stage1/console.log | 18262 ++++++++--------
05-build_linux/console.log | 826 +-
06-build_abe-qemu/console.log | 3482 +--
07-boot_linux/console.log | 494 +-
08-check_regression/console.log | 12 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 12 +-
09-update_baseline/results.regressions | 2 +-
console.log | 34813 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
results | 2 +-
14 files changed, 34822 insertions(+), 34820 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-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 730bfa20 0: update: binutils-gcc-linux-qemu: all
new d6965011 0: update: binutils-gcc-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 (730bfa20)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 | 68 +-
02-prepare_abe/console.log | 68 +-
03-build_abe-binutils/console.log | 11657 ++++++------
04-build_abe-stage1/console.log | 12979 +++++++------
05-build_linux/console.log | 638 +-
06-build_abe-qemu/console.log | 4469 +++--
07-boot_linux/console.log | 2 +-
08-check_regression/console.log | 2 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 2 +-
09-update_baseline/results.regressions | 2 +-
console.log | 29897 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
results | 2 +-
14 files changed, 29888 insertions(+), 29914 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.
unknown user pushed a change to branch master
in repository gcc.
from 5987d8a79cd cris: define DWARF_FRAME_REGISTERS
new e7afb82c358 libstdc++: Uncomment more parts of <chrono> synopsis test
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:
libstdc++-v3/testsuite/std/time/syn_c++20.cc | 5 ++++-
1 file changed, 4 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.
unknown user pushed a change to branch master
in repository gcc.
from 6ceb712e269 tree-optimization/99510 - fix type reuse of build_aligned_type
new 99d5299376d [Vect] Fix mask check on Scatter loads/stores
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:
gcc/testsuite/gcc.dg/vect/pr99102.c | 20 ++++++++++++++++++++
gcc/tree-vect-stmts.c | 4 ++--
2 files changed, 22 insertions(+), 2 deletions(-)
create mode 100644 gcc/testsuite/gcc.dg/vect/pr99102.c
--
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.
unknown user pushed a change to branch master
in repository gcc.
from 99d5299376d [Vect] Fix mask check on Scatter loads/stores
new 3fbac260fc7 [testsuite] Fix target selector for pr99102.c
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:
gcc/testsuite/gcc.dg/vect/pr99102.c | 4 ++--
1 file changed, 2 insertions(+), 2 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-aarch64-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 9d1cb6d3 0: update: binutils-gcc-linux-qemu: all
new c84582cf 0: update: binutils-gcc-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 (9d1cb6d3)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 | 122 +-
02-prepare_abe/console.log | 170 +-
03-build_abe-binutils/console.log | 11728 +++++------
04-build_abe-stage1/console.log | 13734 ++++++-------
05-build_linux/console.log | 822 +-
06-build_abe-qemu/console.log | 4470 +++--
07-boot_linux/console.log | 10 +-
08-check_regression/console.log | 12 +-
08-check_regression/results.regressions | 2 +-
09-update_baseline/console.log | 12 +-
09-update_baseline/results.regressions | 2 +-
console.log | 31080 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
results | 2 +-
14 files changed, 31094 insertions(+), 31086 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.