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-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 8374151d 4: update: llvm-linux: 17561
new b77dce67 4: update: llvm-linux: 17561
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 (8374151d)
\
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:
01-reset_artifacts/console.log | 152 +-
02-build_llvm/console.log | 11652 ++++++++++++-------------
03-build_linux/console.log | 6250 +++++++-------
console.log | 18054 ++++++++++++++++++++-------------------
jenkins/manifest.sh | 12 +-
5 files changed, 18062 insertions(+), 18058 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-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 592e2506 0: update: binutils-gcc-linux: all
new 67dc6f1e 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 (592e2506)
\
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 | 342 +-
03-build_abe-binutils/console.log | 10696 +-
04-build_abe-stage1/console.log | 14562 +-
05-build_linux/console.log | 390264 ++++++++++++++++----------------
06-boot_linux/console.log | 2 +-
console.log | 416082 +++++++++++++++++------------------
jenkins/manifest.sh | 16 +-
8 files changed, 416051 insertions(+), 416079 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_bmk/llvm-master-aarch64-spec2k6-Oz_LTO
in repository toolchain/ci/glibc.
from ac3da35de5 misc/tst-tsearch: Additional explicit error checking
adds 32e902a94e aarch64: thunderx2 memmove performance improvements
No new revisions were added by this update.
Summary of changes:
ChangeLog | 11 +
sysdeps/aarch64/multiarch/ifunc-impl-list.c | 1 +
sysdeps/aarch64/multiarch/memcpy_thunderx2.S | 572 ++++++++++-----------------
sysdeps/aarch64/multiarch/memmove.c | 5 +-
4 files changed, 227 insertions(+), 362 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.