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-stable-defconfig
in repository toolchain/ci/base-artifacts.
discards 46684971 0: good: binutils-gcc-linux: boot
new c21f99b7 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 (46684971)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-st [...]
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:
.../console.log | 34 +-
{2-prepare_abe => 02-prepare_abe}/console.log | 14 +-
.../console.log | 3830 ++++----
.../console.log | 4764 +++++-----
{5-build_linux => 05-build_linux}/console.log | 243 +-
06-boot_linux/console.log | 240 +
.../console.log | 0
.../console.log | 0
6-boot_linux/console.log | 240 -
console.log | 9277 +++++++++-----------
jenkins/manifest.sh | 18 +-
11 files changed, 8817 insertions(+), 9843 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (87%)
rename {2-prepare_abe => 02-prepare_abe}/console.log (97%)
rename {3-build_abe-binutils => 03-build_abe-binutils}/console.log (93%)
rename {4-build_abe-stage1 => 04-build_abe-stage1}/console.log (98%)
rename {5-build_linux => 05-build_linux}/console.log (91%)
create mode 100644 06-boot_linux/console.log
rename {7-check_regression => 07-check_regression}/console.log (100%)
rename {8-update_baseline => 08-update_baseline}/console.log (100%)
delete mode 100644 6-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.
unknown user pushed a change to branch master
in repository clang.
from a67b0501cb [RISCV] Pass -target-abi to -cc1as
new f469a1cb81 update the release notes after the change of 'clang -dumpversion'
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/ReleaseNotes.rst | 2 ++
1 file changed, 2 insertions(+)
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards b74d7e52 0: good: llvm-linux: boot
new b9a5dc60 0: good: 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 (b74d7e52)
\
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:
.../console.log | 34 +-
{2-build_llvm => 02-build_llvm}/console.log | 9334 +++++++++----------
{3-build_linux => 03-build_linux}/console.log | 82 +-
{4-boot_linux => 04-boot_linux}/console.log | 0
.../console.log | 0
.../console.log | 0
console.log | 9448 ++++++++++----------
jenkins/manifest.sh | 10 +-
results | 2 +-
9 files changed, 9477 insertions(+), 9433 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (87%)
rename {2-build_llvm => 02-build_llvm}/console.log (67%)
rename {3-build_linux => 03-build_linux}/console.log (56%)
rename {4-boot_linux => 04-boot_linux}/console.log (100%)
rename {5-check_regression => 05-check_regression}/console.log (100%)
rename {6-update_baseline => 06-update_baseline}/console.log (100%)
--
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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards aa767630 2: good: binutils-gcc-linux: 17538
discards 3050f872 1: first-bad: linux-b517229ca2f7836125be58997808f2803f9ebc86: 17423
discards 9bfeafba 0: good: gcc-f1e03c52e0fb627821e84e514b32dffb11d3ed46: all
new ebe08b2b 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 (aa767630)
\
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:
.../console.log | 34 +-
{2-prepare_abe => 02-prepare_abe}/console.log | 17 +-
.../console.log | 3527 +++--
.../console.log | 4661 +++---
{5-build_linux => 05-build_linux}/console.log | 8349 +++++-----
06-boot_linux/console.log | 8 +
.../console.log | 7 +-
.../console.log | 24 +-
console.log | 15749 ++++++++++---------
jenkins/manifest.sh | 18 +-
results | 4 +-
11 files changed, 16329 insertions(+), 16069 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (87%)
rename {2-prepare_abe => 02-prepare_abe}/console.log (94%)
rename {3-build_abe-binutils => 03-build_abe-binutils}/console.log (94%)
rename {4-build_abe-stage1 => 04-build_abe-stage1}/console.log (98%)
rename {5-build_linux => 05-build_linux}/console.log (97%)
create mode 100644 06-boot_linux/console.log
rename {7-check_regression => 07-check_regression}/console.log (74%)
rename {8-update_baseline => 08-update_baseline}/console.log (77%)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.