This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk/llvm-release-arm-spec2k6-Os_LTO
in repository toolchain/ci/base-artifacts.
discards 7edae16ba 0: reset: binutils-gcc-glibc-llvm: -3
new e34ec43d6 0: reset: binutils-gcc-glibc-llvm: -3
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 (7edae16ba)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/llvm-release-arm-spe [...]
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 | 128 +-
02-prepare_abe/console.log | 438 +-
03-build_abe-binutils/console.log | 9516 +-
04-build_abe-stage1/console.log | 17441 +--
05-build_abe-linux/console.log | 292 +-
06-build_abe-glibc/console.log | 37674 +++----
07-build_abe-stage2/console.log | 46557 ++++----
08-build_llvm-true/console.log | 11636 +-
09-benchmark-Os_LTO_mthumb/benchmark-start.log | 2 +-
09-benchmark-Os_LTO_mthumb/benchmark.log | 5 +-
09-benchmark-Os_LTO_mthumb/console.log | 83 +-
console.log | 124615 +++++++++++-----------
jenkins/manifest.sh | 10 +-
13 files changed, 124208 insertions(+), 124189 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-aarch64-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 2f69ad21e 0: update: binutils-gcc-linux: all
new 21009e771 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 (2f69ad21e)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 | 128 +-
02-prepare_abe/console.log | 306 +-
03-build_abe-binutils/console.log | 11021 +++++++-------
04-build_abe-stage1/console.log | 15630 +++++++++----------
05-build_linux/console.log | 2226 +--
06-boot_linux/console.log | 6 +-
console.log | 29364 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
8 files changed, 29408 insertions(+), 29285 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-master-arm-lts-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 103ac68e1 0: update: llvm-linux: all
new c496904f2 0: update: llvm-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 (103ac68e1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 | 158 +-
02-build_llvm/console.log | 12320 ++++++++++++++++++------------------
03-build_linux/console.log | 824 ++-
04-boot_linux/console.log | 2 +-
console.log | 13304 +++++++++++++++++++--------------------
jenkins/manifest.sh | 8 +-
6 files changed, 13306 insertions(+), 13310 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-master-aarch64-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f217bb646 0: update: llvm-linux: all
new 0f49a725f 0: update: llvm-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 (f217bb646)
\
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 | 178 +-
02-build_llvm/console.log | 12246 +++++++++++++++++------------------
03-build_linux/console.log | 654 +-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 8 +-
console.log | 13113 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
results | 2 +-
9 files changed, 13099 insertions(+), 13124 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 beef423a4f1 Remove dg-add-options c99_runtime
new 1d1555c81c9 2019-10-13 Thomas Koenig <tkoenig(a)gcc.gnu.org>
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/fortran/ChangeLog | 7 +++++++
gcc/fortran/expr.c | 3 +++
gcc/testsuite/ChangeLog | 5 +++++
gcc/testsuite/gfortran.dg/minmaxloc_14.f90 | 12 ++++++++++++
4 files changed, 27 insertions(+)
create mode 100644 gcc/testsuite/gfortran.dg/minmaxloc_14.f90
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.