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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 4a26aef8 0: update: gcc-ef33047a8b93d416f08f3f640dd65f3887fb05c1: boot
new de41e639 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 (4a26aef8)
\
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 | 171 +-
02-prepare_abe/console.log | 232 +-
03-build_abe-binutils/console.log | 11754 ++++++------
04-build_abe-stage1/console.log | 15726 ++++++++--------
05-build_linux/console.log | 637 +-
06-boot_linux/console.log | 614 +-
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 18 +-
08-update_baseline/results.regressions | 2 +-
console.log | 29154 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
12 files changed, 29789 insertions(+), 28541 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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards babbec33 0: update: llvm-linux: boot
new 79f2ff48 0: update: llvm-ef32c611aa214dea855364efd7ba451ec5ec3f74: 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 (babbec33)
\
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 | 225 +-
02-build_llvm/console.log | 12710 ++++++++++++++++-----------------
03-build_linux/console.log | 661 +-
04-boot_linux/console.log | 822 ++-
05-check_regression/console.log | 14 +-
06-update_baseline/console.log | 22 +-
console.log | 14454 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
8 files changed, 14596 insertions(+), 14322 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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 5702dd23 0: update: llvm-linux: boot
new 68fa6489 0: update: llvm-ef32c611aa214dea855364efd7ba451ec5ec3f74: 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 (5702dd23)
\
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 | 112 +-
02-build_llvm/console.log | 12616 +++++++++++++++----------------
03-build_linux/console.log | 1753 ++---
04-boot_linux/console.log | 731 +-
05-check_regression/console.log | 18 +-
06-update_baseline/console.log | 20 +-
console.log | 15250 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
8 files changed, 15368 insertions(+), 15142 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 0770015c 0: update: llvm-linux: 19285
new d94f7df5 0: update: llvm-ef32c611aa214dea855364efd7ba451ec5ec3f74: 19285
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 (0770015c)
\
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 | 184 +-
02-build_llvm/console.log | 12648 +++++++++++++--------------
03-build_linux/console.log | 804 +-
05-check_regression/console.log | 18 +-
05-check_regression/results.regressions | 10 +-
06-update_baseline/console.log | 18 +-
06-update_baseline/results.regressions | 10 +-
console.log | 13695 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
9 files changed, 13578 insertions(+), 13819 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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards f9a88808 0: update: binutils-gcc-linux: boot
new 77dee9f4 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 (f9a88808)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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:
01-reset_artifacts/console.log | 182 +-
02-prepare_abe/console.log | 442 +-
03-build_abe-binutils/console.log | 11485 +++++------
04-build_abe-stage1/console.log | 18289 ++++++++---------
05-build_linux/console.log | 816 +-
06-boot_linux/console.log | 808 +-
07-check_regression/console.log | 12 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 12 +-
08-update_baseline/results.regressions | 2 +-
console.log | 31978 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
12 files changed, 32371 insertions(+), 31671 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 binutils-gdb.
from 9cd7a95a2bb [gdb/testsuite] Fix gdb.base/float128.exp with --with-mpfr=no
new b143e2d506b Fix a build problem when using FreeBSD 12.
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:
binutils/ChangeLog | 6 ++++++
binutils/ar.c | 2 +-
binutils/arsup.c | 2 +-
binutils/objcopy.c | 2 +-
4 files changed, 9 insertions(+), 3 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.