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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards a01cf9da9d 1: last-good: binutils-gcc-linux: 24959
discards 7e723c112f gcc-936f703220810379cade807234565f74a551da87: all
new 0b275502b1 0: last-good: 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 (a01cf9da9d)
\
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:
1-reset_artifacts/console.log | 16 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3011 ++++++++---------
4-build_abe-stage1/console.log | 3478 +++++++++----------
5-count_linux_objs/console.log | 202 +-
6-check_regression/console.log | 12 +-
7-update_baseline/console.log | 32 +-
console.log | 6875 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
results | 2 +-
10 files changed, 6829 insertions(+), 6815 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-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5d95212500 0: last-good: llvm-linux: 17393
new de4caf4055 0: last-good: llvm-linux: 17393
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 (5d95212500)
\
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:
1-reset_artifacts/console.log | 16 +-
2-build_llvm/console.log | 9019 ++++++++++++++++++------------------
3-count_linux_objs/console.log | 537 ++-
console.log | 9846 ++++++++++++++++++++--------------------
jenkins/manifest.sh | 12 +-
5 files changed, 9847 insertions(+), 9583 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards b2aa7d4ce8 0: last-good: llvm-linux: 18201
new 468e828e5e 0: last-good: llvm-linux: 18222
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 (b2aa7d4ce8)
\
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:
1-reset_artifacts/console.log | 70 +-
2-build_llvm/console.log | 10154 +++++++++++++++++-----------------
3-count_linux_objs/console.log | 1139 ++--
4-check_regression/console.log | 16 +-
5-update_baseline/console.log | 18 +-
console.log | 11395 +++++++++++++++++++--------------------
jenkins/manifest.sh | 12 +-
results | 2 +-
8 files changed, 11384 insertions(+), 11422 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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards fc118d88b7 0: last-good: llvm-linux: 16639
new 98febc968e 0: last-good: llvm-linux: 16665
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 (fc118d88b7)
\
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:
1-reset_artifacts/console.log | 71 +-
2-build_llvm/console.log | 10289 +++++++++++++++++-----------------
3-count_linux_objs/console.log | 1337 +++--
4-check_regression/console.log | 16 +-
5-update_baseline/console.log | 18 +-
console.log | 11727 ++++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
results | 2 +-
8 files changed, 11898 insertions(+), 11576 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 clang.
from c46f81b101 [analyzer] MIGChecker: Enable by default as `osx.MIG'.
new 0ce92a1453 revert r354615: [HIP] change kernel stub name
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:
lib/CodeGen/CGCUDANV.cpp | 6 ------
test/CodeGenCUDA/device-stub.cu | 3 +--
2 files changed, 1 insertion(+), 8 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 9221595db9 0: last-good: llvm-linux: all
new cf8f269b36 0: last-good: 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 (9221595db9)
\
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:
1-reset_artifacts/console.log | 17 +-
2-build_llvm/console.log | 9132 ++++++++++++++++++++-------------------
3-count_linux_objs/console.log | 149 +-
5-update_baseline/console.log | 2 +-
console.log | 9346 ++++++++++++++++++++--------------------
jenkins/manifest.sh | 14 +-
6 files changed, 9402 insertions(+), 9258 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.