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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 965abce3 0: update: binutils-gcc-linux: all
new c6f02e0c 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 (965abce3)
\
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 | 193 +-
02-prepare_abe/console.log | 440 +-
03-build_abe-binutils/console.log | 11458 ++++----
04-build_abe-stage1/console.log | 13764 ++++-----
05-build_linux/console.log | 571 +-
06-boot_linux/console.log | 336 -
06-build_abe-qemu/console.log | 2407 ++
07-boot_linux/console.log | 13 +
07-check_regression/results.regressions | 2 -
.../console.log | 12 +-
08-check_regression/results.regressions | 2 +
08-update_baseline/results.regressions | 2 -
.../console.log | 18 +-
09-update_baseline/results.regressions | 2 +
console.log | 29200 ++++++++++---------
jenkins/manifest.sh | 23 +-
results | 2 +-
17 files changed, 31460 insertions(+), 26985 deletions(-)
delete mode 100644 06-boot_linux/console.log
create mode 100644 06-build_abe-qemu/console.log
create mode 100644 07-boot_linux/console.log
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (84%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/results.regressions
rename {08-update_baseline => 09-update_baseline}/console.log (76%)
create mode 100644 09-update_baseline/results.regressions
--
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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards bf6168a2 2: update: binutils-gcc-linux: 19286
new a912ba96 2: update: binutils-gcc-linux-qemu: 19293
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 (bf6168a2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
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 | 111 +-
02-prepare_abe/console.log | 430 +-
03-build_abe-binutils/console.log | 11863 +++---
04-build_abe-stage1/console.log | 20400 +++++-----
05-build_linux/console.log | 6352 +--
07-check_regression/results.regressions | 11 -
.../console.log | 22 +-
08-check_regression/results.regressions | 11 +
08-update_baseline/console.log | 104 -
08-update_baseline/results.regressions | 11 -
09-update_baseline/console.log | 104 +
09-update_baseline/results.regressions | 11 +
console.log | 39294 ++++++++++---------
jenkins/manifest.sh | 22 +-
results | 2 +-
15 files changed, 39387 insertions(+), 39361 deletions(-)
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (74%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/console.log
delete mode 100644 08-update_baseline/results.regressions
create mode 100644 09-update_baseline/console.log
create mode 100644 09-update_baseline/results.regressions
--
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-aarch64-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 5868aa0b 0: update: linux-7bba37a1591369e2e506d599b8f5d7d0516b2dbc: boot
new b708609f 0: update: qemu-aa14de086675280206dbc1849da6f85b75f62f1b: 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 (5868aa0b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 | 234 +-
02-prepare_abe/console.log | 446 +-
03-build_llvm/console.log | 13110 +++++++++++------------
04-build_linux/console.log | 572 +-
05-build_abe-qemu/console.log | 6788 ++++++------
06-boot_linux/console.log | 494 +-
07-check_regression/console.log | 62 +-
08-update_baseline/console.log | 82 +-
console.log | 21788 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
10 files changed, 21578 insertions(+), 22008 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 773a4106bbb go-test.exp: retain any characters at end of ERROR line
new 06ff8708f0b gcc: xtensa: fix PR target/98285
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/config/xtensa/predicates.md | 5 ++-
gcc/config/xtensa/xtensa.md | 18 +++++++----
gcc/testsuite/gcc.target/xtensa/pr98285.c | 54 +++++++++++++++++++++++++++++++
3 files changed, 68 insertions(+), 9 deletions(-)
create mode 100644 gcc/testsuite/gcc.target/xtensa/pr98285.c
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.