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-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 00f9db9e 0: update: binutils-gcc-linux: all
new a079314f 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 (00f9db9e)
\
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 | 58 +-
02-prepare_abe/console.log | 434 +-
03-build_abe-binutils/console.log | 11632 ++++++++--------
04-build_abe-stage1/console.log | 13656 +++++++++---------
05-build_linux/console.log | 778 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 2 +-
08-update_baseline/console.log | 4 +-
console.log | 26566 ++++++++++++++++++------------------
jenkins/manifest.sh | 10 +-
regressions.txt | 3 +-
11 files changed, 26573 insertions(+), 26572 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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 7301946b 10: update: llvm-linux: 17560
new 8ca62c76 10: update: llvm-linux: 17560
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 (7301946b)
\
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 | 128 +-
02-build_llvm/console.log | 12676 ++++++++++++-------------
03-build_linux/console.log | 6180 ++++++------
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 124 +-
console.log | 19110 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
regressions.txt | 20 +-
8 files changed, 19125 insertions(+), 19125 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
in repository toolchain/ci/interesting-commits.
from 3230059 Add regression 56cc3af4e8c8eaba91b51efa6081a868adbd97c3 from [...]
new 3171642 Add regression 56cc3af4e8c8eaba91b51efa6081a868adbd97c3 from [...]
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:
linux | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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 da5f369df6d Fix broken type comparison assert
new f32a3662cda libstdc++: Fix std::string error in Debug Mode
new b112e3cb602 libstdc++: Fix std::span test failures with _GLIBCXX_ASSERTIONS
new ae7051590d4 libstdc++: Define <=> for Debug Mode array
The 3 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 | 24 ++++++++++++++++++++++
libstdc++-v3/include/debug/array | 20 ++++++++++++++++++
libstdc++-v3/include/debug/string | 2 +-
.../array/tuple_interface/get_debug_neg.cc | 6 +++---
.../tuple_interface/tuple_element_debug_neg.cc | 2 +-
.../23_containers/span/back_assert_neg.cc | 1 +
.../23_containers/span/first_2_assert_neg.cc | 1 +
.../23_containers/span/first_assert_neg.cc | 1 +
.../23_containers/span/front_assert_neg.cc | 1 +
.../23_containers/span/index_op_assert_neg.cc | 1 +
.../23_containers/span/last_2_assert_neg.cc | 1 +
.../23_containers/span/last_assert_neg.cc | 1 +
.../23_containers/span/subspan_2_assert_neg.cc | 1 +
.../23_containers/span/subspan_3_assert_neg.cc | 1 +
.../23_containers/span/subspan_4_assert_neg.cc | 1 +
.../23_containers/span/subspan_5_assert_neg.cc | 1 +
.../23_containers/span/subspan_6_assert_neg.cc | 1 +
.../23_containers/span/subspan_assert_neg.cc | 1 +
18 files changed, 62 insertions(+), 5 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-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 9ad36df8 2: update: llvm-linux: 18456
new 373dd7f5 2: update: llvm-linux: 18456
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 (9ad36df8)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-m [...]
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 | 175 +-
02-build_llvm/console.log | 12770 +++++++++++++++++-----------------
03-build_linux/console.log | 842 +--
05-check_regression/console.log | 14 +-
06-update_baseline/console.log | 122 +-
console.log | 13923 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
regressions.txt | 6 +-
8 files changed, 13942 insertions(+), 13924 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-stable-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 161def26 0: update: llvm-linux: all
new 2656e144 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 (161def26)
\
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 | 162 +-
02-build_llvm/console.log | 12670 ++++++++--------
03-build_linux/console.log | 16578 ++++++++++-----------
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 4 +-
console.log | 29418 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
8 files changed, 29423 insertions(+), 29423 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.