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-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 53321a3c 2: update: binutils-gcc-linux: 17559
new 578d3096 2: update: binutils-gcc-linux: 17559
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 (53321a3c)
\
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 | 424 +-
03-build_abe-binutils/console.log | 12144 +++++-----
04-build_abe-stage1/console.log | 16203 +++++++-------
05-build_linux/console.log | 6394 +++---
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 20 +-
08-update_baseline/console.log | 10 +-
08-update_baseline/results.regressions | 20 +-
console.log | 35305 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
11 files changed, 35370 insertions(+), 35292 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 a68a3ec7 2: update: llvm-linux: 20707
new 7e1571ef 2: update: llvm-linux: 20707
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 (a68a3ec7)
\
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 | 13308 +++++++++++++--------------
03-build_linux/console.log | 860 +-
05-check_regression/console.log | 10 +-
05-check_regression/results.regressions | 12 +-
06-update_baseline/console.log | 146 +-
06-update_baseline/results.regressions | 12 +-
console.log | 14452 +++++++++++++++---------------
jenkins/manifest.sh | 12 +-
9 files changed, 14474 insertions(+), 14466 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards b91f00c1 2: update: llvm-linux: 5685
new c941b705 2: update: llvm-linux: 5685
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 (b91f00c1)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-s [...]
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 | 13398 +++++++++++++--------------
03-build_linux/console.log | 980 +-
05-check_regression/console.log | 2 +-
05-check_regression/results.regressions | 4 +-
06-update_baseline/console.log | 78 +-
06-update_baseline/results.regressions | 4 +-
console.log | 14624 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
9 files changed, 14634 insertions(+), 14630 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 e1a1808cd19 c++: Fix bootstrap failure. [PR97118]
new c89956cba9d analyzer: handle strdup and strndup
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/analyzer/sm-malloc.cc | 4 +++-
gcc/testsuite/gcc.dg/analyzer/strdup-1.c | 21 +++++++++++++++++++++
gcc/testsuite/gcc.dg/analyzer/strndup-1.c | 21 +++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
create mode 100644 gcc/testsuite/gcc.dg/analyzer/strdup-1.c
create mode 100644 gcc/testsuite/gcc.dg/analyzer/strndup-1.c
--
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-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 70c22e71 2: update: llvm-linux: 20966
new 2ef3c8a6 2: update: llvm-linux: 20983
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 (70c22e71)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/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 | 128 +-
02-build_llvm/console.log | 12613 +++++++++++++--------------
03-build_linux/console.log | 848 +-
05-check_regression/console.log | 18 +-
05-check_regression/results.regressions | 8 +-
06-update_baseline/console.log | 50 +-
06-update_baseline/results.regressions | 8 +-
console.log | 13657 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
results | 2 +-
10 files changed, 13673 insertions(+), 13667 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.