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-defconfig
in repository toolchain/ci/base-artifacts.
discards 3e6b063a4 binutils-be6d4f74c77c6f521afc873d226480e001cb99c2: all
new d6f189ed8 gcc-50c4a518122023d58df32ad4514e430517ab3c40: 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 (3e6b063a4)
\
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:
1-reset_artifacts/console.log | 74 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6410 ++++----
4-build_abe-stage1/console.log | 9540 +++++------
5-count_linux_objs/console.log | 15813 +++++++++---------
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 31851 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 31519 insertions(+), 32221 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 lldb.
from e29cec1fb Fix test after AST dump output change
new b5086412d [Test] Fix up tests affected by the new LLVM header.
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:
lit/ExecControl/StopHook/Inputs/stop-hook-2.lldbinit | 2 +-
lit/ExecControl/StopHook/Inputs/stop-hook-3.lldbinit | 2 +-
lit/Reproducer/Inputs/GDBRemoteCapture.in | 2 +-
lit/Reproducer/Inputs/GDBRemoteReplay.in | 2 +-
.../TestBreakpointByLineAndColumn.py | 8 ++++----
.../data-formatter-stl/libcxx/function/TestLibCxxFunction.py | 6 +++---
.../lldbsuite/test/lang/objc/exceptions/TestObjCExceptions.py | 10 +++++-----
7 files changed, 16 insertions(+), 16 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/gnu-release-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 75df71b44 gcc-d67e09824ded3f934d1fb00fd526d31d34598d56: all
new 21cc8b5ca linux-f8ff6c732d35904d773043f979b844ef330c701b: 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 (75df71b44)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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:
1-reset_artifacts/console.log | 78 +-
2-prepare_abe/console.log | 30 +-
3-build_abe-binutils/build-ok | 0
3-build_abe-binutils/console.log | 6277 +++++++------
4-build_abe-stage1/build-ok | 0
4-build_abe-stage1/console.log | 11896 ++++++++++++------------
5-count_linux_objs/console.log | 158 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 18413 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 6 +-
trigger-bisect-on-failure | 6 +-
15 files changed, 18448 insertions(+), 18438 deletions(-)
delete mode 100644 3-build_abe-binutils/build-ok
delete mode 100644 4-build_abe-stage1/build-ok
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 17e64efd8 llvm-e264daec97935db606c312b10e43f4e35ac39b58: all
new 35104c9ca linux-a790195efdddfc013e1ec4a95452863dab4a8fc9: 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 (17e64efd8)
\
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 | 130 +-
2-build_llvm/build-ok | 0
2-build_llvm/console.log | 9242 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 182 +-
console.log | 9534 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 24 +-
results | 4 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 9576 insertions(+), 9550 deletions(-)
delete mode 100644 2-build_llvm/build-ok
--
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/gnu-release-aarch64-lts-defconfig
in repository toolchain/ci/binutils-gdb.
from 6b53149a41 Automatic date update in version.in
adds 8d87b79d2a Automatic date update in version.in
adds 595d73421b Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 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.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 8696fba86 gcc-8950675bcdcb5783503089aa76c7bf584eeb218e: all
new d661954ae binutils-595d73421b2f56d343c8e0f32cef8c073f3dad70: 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 (8696fba86)
\
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 | 72 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6530 ++++++++--------
4-build_abe-stage1/console.log | 8617 ++++++++++-----------
5-count_linux_objs/console.log | 138 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 15475 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 15503 insertions(+), 15381 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.