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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards b5c9661e 0: update: binutils-gcc-linux: all
new f8877ae7 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 (b5c9661e)
\
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 | 182 +-
02-prepare_abe/console.log | 432 +-
03-build_abe-binutils/console.log | 11133 ++++++-------
04-build_abe-stage1/console.log | 18071 ++++++++++-----------
05-build_linux/console.log | 880 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 10 +-
08-update_baseline/console.log | 10 +-
console.log | 30741 ++++++++++++++++++------------------
jenkins/manifest.sh | 8 +-
10 files changed, 30771 insertions(+), 30698 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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 48d3e0f1 0: update: llvm-linux: boot
new bc5a072b 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 (48d3e0f1)
\
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 | 166 +-
02-build_llvm/console.log | 12578 +++++++++++++++++------------------
03-build_linux/console.log | 878 ++-
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 13657 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 13660 insertions(+), 13635 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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5504444b 11: update: llvm-linux: 16048
new ea9e9a73 11: 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 (5504444b)
\
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 | 120 +-
02-build_llvm/console.log | 12782 ++++++++++++------------
03-build_linux/console.log | 7528 +++++++-------
05-check_regression/console.log | 10 +-
06-update_baseline/console.log | 108 +-
console.log | 20548 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
7 files changed, 20556 insertions(+), 20548 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 2907ec5f 10: update: llvm-linux: 16048
new d0ba68f3 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 (2907ec5f)
\
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 | 182 +-
02-build_llvm/console.log | 12580 ++++++++++++------------
03-build_linux/console.log | 6795 +++++++------
05-check_regression/console.log | 10 +-
06-update_baseline/console.log | 28 +-
console.log | 19595 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
7 files changed, 19600 insertions(+), 19602 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 5586e5060fb libstdc++: Forward second argument of views::iota using the [...]
new 6e63438a0d7 libstdc++: Fix capturing of lvalue references in_RangeAdapt [...]
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/ChangeLog | 8 ++++
libstdc++-v3/include/std/ranges | 50 ++++++++++++++++++++--
.../testsuite/std/ranges/adaptors/split.cc | 18 ++++++++
.../ranges/adaptors/{elements.cc => split_neg.cc} | 39 ++++++++---------
4 files changed, 91 insertions(+), 24 deletions(-)
copy libstdc++-v3/testsuite/std/ranges/adaptors/{elements.cc => split_neg.cc} (56%)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.