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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 510eb2ef0 0: update: binutils-gcc-linux: all
new b8609cd7b 0: update: binutils-gcc-linux: 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 (510eb2ef0)
\
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 | 239 +-
02-prepare_abe/console.log | 446 +-
03-build_abe-binutils/console.log | 11644 +++++------
04-build_abe-stage1/console.log | 20366 +++++++++---------
05-build_linux/console.log | 670 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 12 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 14 +-
08-update_baseline/results.regressions | 2 +-
console.log | 33491 +++++++++++++++---------------
jenkins/manifest.sh | 16 +-
12 files changed, 33459 insertions(+), 33445 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-defconfig
in repository toolchain/ci/gcc.
from 5420d2d0ffa Daily bump.
adds df52e2f8fc8 aarch64: Add support for Neoverse N2 CPU
adds b35353f96be s390: Fix up s390_atomic_assign_expand_fenv
adds 472396ebbca AArch64: Add rng feature to Neoverse V1
adds 19870c2b458 AArch64: Add prefer_advsimd_autovec internal tune_flag
adds 3f7059376b7 Daily bump.
No new revisions were added by this update.
Summary of changes:
gcc/ChangeLog | 29 +++++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/config/aarch64/aarch64-cores.def | 7 +++++--
gcc/config/aarch64/aarch64-tune.md | 2 +-
gcc/config/aarch64/aarch64-tuning-flags.def | 3 +++
gcc/config/aarch64/aarch64.c | 13 +++++++++++--
gcc/config/s390/s390.c | 17 +++++++++--------
gcc/doc/invoke.texi | 6 +++---
8 files changed, 62 insertions(+), 17 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 859fc8853 0: update: binutils-gcc-linux: boot
new 132df37d1 0: update: binutils-gcc-linux: 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 (859fc8853)
\
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 | 190 +-
02-prepare_abe/console.log | 424 +-
03-build_abe-binutils/console.log | 11274 +++++------
04-build_abe-stage1/console.log | 18045 ++++++++---------
05-build_linux/console.log | 688 +-
06-boot_linux/console.log | 495 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 2 +-
08-update_baseline/results.regressions | 2 +-
console.log | 31120 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
results | 2 +-
13 files changed, 31133 insertions(+), 31125 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/llvm-release-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 588f37490 10: update: llvm-linux: 16048
new 9cb5afcd8 10: update: llvm-linux: 16048
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 (588f37490)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-aarc [...]
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 | 172 +-
02-build_llvm/console.log | 12660 +++++++++----------
03-build_linux/console.log | 6640 +++++-----
05-check_regression/console.log | 2 +-
05-check_regression/results.regressions | 20 +-
06-update_baseline/console.log | 6 +-
06-update_baseline/results.regressions | 20 +-
console.log | 19480 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
9 files changed, 19504 insertions(+), 19504 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_bmk_tk1/llvm-release-arm-spec2k6-O2_LTO
in repository toolchain/ci/base-artifacts.
discards 6485f05c6 0: update: binutils-gcc-glibc-llvm: 1
new ab9082178 0: update: binutils-gcc-glibc: 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 (6485f05c6)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tk1/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 | 119 +-
02-prepare_abe/console.log | 240 +-
03-build_abe-binutils/console.log | 10974 +-
04-build_abe-stage1/console.log | 18182 ++--
05-build_abe-linux/console.log | 294 +-
06-build_abe-glibc/console.log | 34857 +++----
07-build_abe-stage2/console.log | 43602 ++++----
08-build_llvm-true/console.log | 12578 ++-
10-benchmark--O2_LTO_marm/benchmark-start.log | 2 +-
10-benchmark--O2_LTO_marm/benchmark.log | 4 +-
10-benchmark--O2_LTO_marm/console.log | 98 +-
11-check_regression/console.log | 751 +-
11-check_regression/results-0.csv | 120 +-
11-check_regression/results-1.csv | 117 +-
11-check_regression/results-brief.csv | 38 +-
11-check_regression/results-compare.csv | 1 +
11-check_regression/results-full.csv | 121 +-
11-check_regression/results.csv | 47 +-
11-check_regression/results.log | 2598 +-
12-update_baseline/console.log | 759 +-
12-update_baseline/results-0.csv | 120 +-
12-update_baseline/results-1.csv | 117 +-
12-update_baseline/results-brief.csv | 38 +-
12-update_baseline/results-compare.csv | 1 +
12-update_baseline/results-full.csv | 121 +-
12-update_baseline/results.csv | 47 +-
12-update_baseline/results.log | 2646 +-
console.log | 122600 +++++++++++------------
jenkins/manifest.sh | 14 +-
results_id | 2 +-
30 files changed, 125455 insertions(+), 125753 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.