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 cac7465 0: update: binutils-gcc-linux: boot
new 799799d 0: update: binutils-gcc-linux: boot
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 (cac7465)
\
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 | 166 +-
02-prepare_abe/console.log | 432 +-
03-build_abe-binutils/console.log | 11078 +++++++-------
04-build_abe-stage1/console.log | 15631 ++++++++++----------
05-build_linux/console.log | 816 +-
06-boot_linux/console.log | 408 +-
console.log | 28556 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
8 files changed, 28583 insertions(+), 28516 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards f26128e 0: update: llvm-linux: 19708
new bfdbe3b 0: update: llvm-linux: 19716
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 (f26128e)
\
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 | 130 +-
02-build_llvm/console.log | 12024 ++++++++++++++---------------
03-build_linux/console.log | 3346 ++++----
05-check_regression/console.log | 8 +-
06-update_baseline/console.log | 6 +-
console.log | 15514 +++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
results | 2 +-
8 files changed, 15535 insertions(+), 15507 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 0b3ff9ae241 [ARM] MVE trunc to i1 vectors
new dbd9cc38a90 [llvm-objcopy] Allow 'protected' visibility to be set when [...]
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:
docs/CommandGuide/llvm-objcopy.rst | 1 +
test/tools/llvm-objcopy/ELF/add-symbol.test | 12 +++++++-----
tools/llvm-objcopy/CopyConfig.cpp | 1 +
tools/llvm-objcopy/ObjcopyOpts.td | 2 +-
4 files changed, 10 insertions(+), 6 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-master-aarch64-stable-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 601a458 0: update: binutils-gcc-linux: all
new fa591c0 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 (601a458)
\
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 | 220 +-
02-prepare_abe/console.log | 412 +-
03-build_abe-binutils/console.log | 11649 +++++++--------
04-build_abe-stage1/console.log | 15658 ++++++++++----------
05-build_linux/console.log | 844 +-
06-boot_linux/console.log | 2 +-
07-check_regression/console.log | 8 +-
08-update_baseline/console.log | 8 +-
console.log | 28820 ++++++++++++++++++------------------
jenkins/manifest.sh | 12 +-
10 files changed, 28838 insertions(+), 28795 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.