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.
from f6e5804903 0: good: llvm-linux: 16671
new 94fe2e367e 1: first-bad: linux-c3619a482e15d98e1d2eb6b32952e753077e7545: 16548
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 | 16 +-
2-build_llvm/console.log | 9225 ++++++++++++++++----------------
3-build_linux/console.log | 1928 ++++---
5-check_regression/console.log | 16 +-
6-update_baseline/console.log | 14 +-
console.log | 11181 ++++++++++++++++++++-------------------
jenkins/manifest.sh | 15 +-
reset-baseline | 0
results | 2 +-
9 files changed, 11555 insertions(+), 10842 deletions(-)
create mode 100644 reset-baseline
--
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-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 19a2c49dea 0: good: binutils-gcc-linux: boot
new b1f169e6d5 0: good: 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 (19a2c49dea)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-lt [...]
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 | 16 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3849 +++---
4-build_abe-stage1/console.log | 5072 ++++---
5-build_linux/console.log | 8943 ++++++------
6-boot_linux/console.log | 390 +-
console.log | 26938 ++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
8 files changed, 21993 insertions(+), 23233 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 e1d072c11d 0: good: llvm-linux: boot
new 71c3d661bf 0: good: llvm-bb92074a2786bfc9ff478adf60ad09056b85d5fc: 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 (e1d072c11d)
\
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:
1-reset_artifacts/console.log | 16 +-
2-build_llvm/console.log | 5451 ++++++++++++++++++++-------------------
3-build_linux/console.log | 93 +-
5-check_regression/console.log | 2 +-
6-update_baseline/console.log | 2 +-
console.log | 5564 +++++++++++++++++++++-------------------
jenkins/manifest.sh | 13 +-
7 files changed, 5762 insertions(+), 5379 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-aarch64-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 2dfef88420 0: good: binutils-gcc-linux: all
new fea240377a 0: good: 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 (2dfef88420)
\
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 | 14 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3388 +++++++++---------
4-build_abe-stage1/console.log | 3783 ++++++++++----------
5-build_linux/console.log | 155 +-
6-boot_linux/console.log | 2 +-
console.log | 7242 +++++++++++++++++++-------------------
jenkins/manifest.sh | 14 +-
results | 2 +-
9 files changed, 7300 insertions(+), 7304 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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 25e56d6bdc 0: good: binutils-88739f776b733b0b84600b283417f862a010bb5d: all
new 87a1b871f0 0: good: gcc-ac4cc85d34badee6be7ee2c4054e9166cdf4872e: 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 (25e56d6bdc)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]
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 | 13 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3738 +++++++++---------
4-build_abe-stage1/console.log | 3932 +++++++++----------
5-build_linux/console.log | 92 +-
6-boot_linux/console.log | 2 +-
console.log | 7781 +++++++++++++++++++-------------------
jenkins/manifest.sh | 8 +-
8 files changed, 7766 insertions(+), 7804 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.