This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk/gnu-release-arm-spec2k6-Os_LTO
in repository toolchain/ci/base-artifacts.
discards 6c9978bfe9 gcc-c8325216a3d4f5f871020365c87dc1346024c766: 0
new 29b2a607ba gcc-6142f179ac2e366e194efd6409e01d624d034ed1: 0
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 (6c9978bfe9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/gnu-release-arm-spec [...]
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:
.../console.log | 67 +-
{2-prepare_abe => 02-prepare_abe}/console.log | 26 +-
.../console.log | 6219 +-
.../console.log | 11862 ++--
.../console.log | 66 +-
.../console.log | 21536 +++---
.../console.log | 29866 ++++----
{8-benchmark => 08-benchmark}/console.log | 44 +-
.../console.log | 211 +-
10-update_baseline/console.log | 213 +-
console.log | 70192 ++++++++++---------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 16 +-
results.csv | 243 +-
results_id | 2 +-
trigger-bisect-on-failure | 4 +-
17 files changed, 70407 insertions(+), 70164 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (68%)
rename {2-prepare_abe => 02-prepare_abe}/console.log (89%)
rename {3-build_abe-binutils => 03-build_abe-binutils}/console.log (63%)
rename {4-build_abe-stage1 => 04-build_abe-stage1}/console.log (59%)
rename {5-build_abe-linux => 05-build_abe-linux}/console.log (79%)
rename {6-build_abe-glibc => 06-build_abe-glibc}/console.log (72%)
rename {7-build_abe-stage2 => 07-build_abe-stage2}/console.log (58%)
rename {8-benchmark => 08-benchmark}/console.log (74%)
rename {9-check_regression => 09-check_regression}/console.log (68%)
--
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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 460f48be88 llvm-f66fbcfb52f58e41d91fc73835cff3b9b076d74d: 19127
new a5073d0906 linux-cd984a5be21549273a3f13b52a8b7b84097b32a7: 19127
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 (460f48be88)
\
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 | 9067 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 625 ++-
console.log | 9768 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9684 insertions(+), 9812 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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 3823113a78 llvm-5ef88bdb68234b21b2ecda683dfe2f76513502d9: 16
new 0394d3524d llvm-d3107a7b85eb8421d91b93bd67d8f0cf769d978e: 16
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 (3823113a78)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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:
1-reset_artifacts/console.log | 14 +-
2-build_llvm/console.log | 9021 +++++++++++++++++++--------------------
3-count_linux_objs/console.log | 41 +-
console.log | 9070 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
8 files changed, 9073 insertions(+), 9089 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 llvm.
from 2e3ef196ba3 [BPF] [BTF] Process FileName with absolute path correctly
new 7ab3c4f0854 Revert "Bump minimum toolchain version"
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:
CMakeLists.txt | 5 +--
cmake/modules/CheckCompilerVersion.cmake | 72 ++++++++++----------------------
docs/CMake.rst | 4 --
docs/GettingStarted.rst | 46 ++++++++------------
4 files changed, 40 insertions(+), 87 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 llvm.
from d9a8f328e91 Bump minimum toolchain version
new 2e3ef196ba3 [BPF] [BTF] Process FileName with absolute path correctly
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/Target/BPF/BTFDebug.cpp | 2 +-
test/CodeGen/BPF/BTF/{func-void.ll => filename.ll} | 49 ++++++++++++----------
2 files changed, 29 insertions(+), 22 deletions(-)
copy test/CodeGen/BPF/BTF/{func-void.ll => filename.ll} (51%)
--
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-tools-extra.
from 3531ea17 [clangd] Expose SelectionTree to code tweaks, and use it for [...]
new b5ed3914 [Clangd] textDocument/definition and textDocument/declaration [...]
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:
clangd/ClangdLSPServer.cpp | 40 ++++++++++++++++++++++++++++++-------
test/clangd/xrefs.test | 49 ++++++++++++++++++++++++++++++++++++++--------
2 files changed, 74 insertions(+), 15 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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards c3a2350c39 linux-dc4c899977350728714d44b6e0d39673f6a97281: all
new bd8948eb20 llvm-b96362ffa9ceecf2256373f2e86a3e62780c599f: 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 (c3a2350c39)
\
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 | 14 +-
2-build_llvm/console.log | 5198 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 179 +-
console.log | 5391 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 5308 insertions(+), 5494 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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 6156c7af1b linux-dc4c899977350728714d44b6e0d39673f6a97281: 19177
new 1d1ee85e46 llvm-a50489754a60000887c13a04b85c772e867e807a: 19177
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 (6156c7af1b)
\
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:
1-reset_artifacts/console.log | 72 +-
2-build_llvm/console.log | 10315 +++++++++++++++++------------------
3-count_linux_objs/console.log | 717 ++-
4-check_regression/console.log | 16 +-
5-update_baseline/console.log | 44 +-
console.log | 11224 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
results | 2 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 11165 insertions(+), 11245 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.