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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards c03bbda86 0: update: llvm-linux: boot
new 170eb8dea 0: update: llvm-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 (c03bbda86)
\
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 | 128 +-
02-build_llvm/console.log | 12856 +++++++++++++++++------------------
03-build_linux/console.log | 618 +-
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 13646 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 13651 insertions(+), 13613 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-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 81646da61 0: update: llvm-linux: boot
new 4901f35dc 0: update: llvm-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 (81646da61)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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 | 128 +-
02-build_llvm/console.log | 13054 +++++++++++++++++------------------
03-build_linux/console.log | 582 +-
04-boot_linux/console.log | 414 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 14180 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 14185 insertions(+), 14185 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-stable-allyesconfig
in repository toolchain/ci/base-artifacts.
discards d07394f58 0: update: binutils-gcc-linux: all
new 1715ff78e 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 (d07394f58)
\
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 | 14 +-
02-prepare_abe/console.log | 406 +-
03-build_abe-binutils/console.log | 11681 ++++++------
04-build_abe-stage1/console.log | 15822 ++++++++--------
05-build_linux/console.log | 764 +-
06-boot_linux/console.log | 6 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 10 +-
08-update_baseline/results.regressions | 2 +-
console.log | 28711 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 28667 insertions(+), 28765 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 7f52a54e8 0: update: binutils-gcc-linux: boot
new a97607c27 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 (7f52a54e8)
\
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 | 102 +-
02-prepare_abe/console.log | 430 +-
03-build_abe-binutils/console.log | 11198 +++++++------
04-build_abe-stage1/console.log | 13499 ++++++++-------
05-build_linux/console.log | 606 +-
06-boot_linux/console.log | 352 +-
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 | 26241 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
12 files changed, 26171 insertions(+), 26277 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 392bc7d2130 Daily bump.
new d176184d98a PR fortran/95106 - truncation of long symbol names with EQU [...]
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 | 6 ++++++
gcc/fortran/trans-common.c | 5 +++--
gcc/testsuite/ChangeLog | 5 +++++
gcc/testsuite/gfortran.dg/equiv_11.f90 | 12 ++++++++++++
4 files changed, 26 insertions(+), 2 deletions(-)
create mode 100644 gcc/testsuite/gfortran.dg/equiv_11.f90
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.