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-arm-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 25317ffc 2: update: binutils-gcc-linux: 4796
discards 03264700 1: reset: gcc-ae7a23a3fab74ebd45203d48fa09681c9945ee7a: 4796
discards 30926077 0: update: binutils-b5e72fb54a432e5d2b572ce605dd04629491a30f: boot
new d3279d52 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 (25317ffc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ne [...]
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 | 119 +-
02-prepare_abe/console.log | 436 +-
03-build_abe-binutils/console.log | 11721 ++--
04-build_abe-stage1/console.log | 20360 +++---
05-build_linux/console.log | 65957 +-------------------
06-boot_linux/console.log | 253 +
07-check_regression/console.log | 23 +-
07-check_regression/results.regressions | 11 +-
08-update_baseline/console.log | 147 +-
08-update_baseline/results.regressions | 11 +-
console.log | 99020 +++++-------------------------
jenkins/manifest.sh | 16 +-
results | 6 +-
13 files changed, 34059 insertions(+), 164021 deletions(-)
create mode 100644 06-boot_linux/console.log
--
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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 924a6d3c 2: update: llvm-linux: 19193
new 59fbab58 2: update: llvm-ef32c611aa214dea855364efd7ba451ec5ec3f74: 19193
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 (924a6d3c)
\
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 | 24 +-
02-build_llvm/console.log | 12608 ++++++++++++++--------------
03-build_linux/console.log | 641 +-
05-check_regression/console.log | 2 +-
05-check_regression/results.regressions | 2 +-
06-update_baseline/console.log | 12 +-
06-update_baseline/results.regressions | 2 +-
console.log | 13287 +++++++++++++++---------------
jenkins/manifest.sh | 8 +-
9 files changed, 13163 insertions(+), 13423 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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 8bec62e2 0: update: llvm-linux: boot
new a086d76d 0: update: llvm-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 (8bec62e2)
\
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 | 216 +-
02-build_llvm/console.log | 12548 +++++++++++++++++-----------------
03-build_linux/console.log | 880 +--
04-boot_linux/console.log | 4 +-
05-check_regression/console.log | 14 +-
06-update_baseline/console.log | 12 +-
console.log | 13674 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 13680 insertions(+), 13676 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 603c8e30 0: update: llvm-linux: all
new 677d092c 0: update: llvm-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 (603c8e30)
\
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 | 182 +-
02-build_llvm/console.log | 12442 ++++++++++++++--------------
03-build_linux/console.log | 3991 +++++----
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 16 +-
06-update_baseline/console.log | 14 +-
console.log | 16647 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
results | 2 +-
9 files changed, 16613 insertions(+), 16691 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.