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-next-allmodconfig
in repository toolchain/ci/base-artifacts.
discards d2352281 2: update: binutils-gcc-linux: 21191
new 81cb5b09 2: update: binutils-gcc-linux: 21201
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 (d2352281)
\
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 | 184 +-
02-prepare_abe/console.log | 390 +-
03-build_abe-binutils/console.log | 11106 +++----
04-build_abe-stage1/console.log | 16027 +++++-----
05-build_linux/console.log | 1206 +-
07-check_regression/results.regressions | 11 -
.../console.log | 24 +-
08-check_regression/results.regressions | 11 +
08-update_baseline/console.log | 171 -
08-update_baseline/results.regressions | 11 -
09-update_baseline/console.log | 104 +
09-update_baseline/results.regressions | 11 +
console.log | 29270 +++++++++----------
jenkins/manifest.sh | 22 +-
results | 2 +-
15 files changed, 29218 insertions(+), 29332 deletions(-)
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (72%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/console.log
delete mode 100644 08-update_baseline/results.regressions
create mode 100644 09-update_baseline/console.log
create mode 100644 09-update_baseline/results.regressions
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 99cb88d5 0: update: llvm-linux: boot
new 1e50ed39 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 (99cb88d5)
\
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 | 87 +-
02-build_llvm/console.log | 6416 -------
02-prepare_abe/console.log | 254 +
03-build_linux/console.log | 497 -
03-build_llvm/console.log | 6416 +++++++
04-boot_linux/console.log | 334 -
04-build_linux/console.log | 498 +
05-build_abe-qemu/console.log | 2408 +++
06-boot_linux/console.log | 12 +
.../console.log | 12 +-
.../results.regressions | 0
.../console.log | 12 +-
.../results.regressions | 0
console.log | 16518 +++++++++++--------
jenkins/manifest.sh | 11 +-
15 files changed, 19071 insertions(+), 14404 deletions(-)
delete mode 100644 02-build_llvm/console.log
create mode 100644 02-prepare_abe/console.log
delete mode 100644 03-build_linux/console.log
create mode 100644 03-build_llvm/console.log
delete mode 100644 04-boot_linux/console.log
create mode 100644 04-build_linux/console.log
create mode 100644 05-build_abe-qemu/console.log
create mode 100644 06-boot_linux/console.log
rename {05-check_regression => 07-check_regression}/console.log (84%)
rename {05-check_regression => 07-check_regression}/results.regressions (100%)
rename {06-update_baseline => 08-update_baseline}/console.log (85%)
rename {06-update_baseline => 08-update_baseline}/results.regressions (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/llvm-release-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 69741ccc 8: update: llvm-linux: 16049
new 8b654063 8: update: llvm-linux: 16049
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 (69741ccc)
\
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 | 174 +-
02-build_llvm/console.log | 6416 ------
02-prepare_abe/console.log | 254 +
03-build_linux/console.log | 3386 ----
03-build_llvm/console.log | 6416 ++++++
04-build_linux/console.log | 3387 ++++
05-check_regression/results.regressions | 11 -
06-update_baseline/results.regressions | 11 -
.../console.log | 12 +-
07-check_regression/results.regressions | 11 +
.../console.log | 32 +-
08-update_baseline/results.regressions | 11 +
console.log | 19697 ++++++++++---------
jenkins/manifest.sh | 10 +-
14 files changed, 20170 insertions(+), 19658 deletions(-)
delete mode 100644 02-build_llvm/console.log
create mode 100644 02-prepare_abe/console.log
delete mode 100644 03-build_linux/console.log
create mode 100644 03-build_llvm/console.log
create mode 100644 04-build_linux/console.log
delete mode 100644 05-check_regression/results.regressions
delete mode 100644 06-update_baseline/results.regressions
rename {05-check_regression => 07-check_regression}/console.log (86%)
create mode 100644 07-check_regression/results.regressions
rename {06-update_baseline => 08-update_baseline}/console.log (88%)
create mode 100644 08-update_baseline/results.regressions
--
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 57d019b8 0: update: binutils-gcc-linux: all
new 74da3514 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 (57d019b8)
\
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:
01-reset_artifacts/console.log | 217 +-
02-prepare_abe/console.log | 316 +-
03-build_abe-binutils/console.log | 11403 +++---
04-build_abe-stage1/console.log | 18206 ++++-----
05-build_linux/console.log | 4926 +--
06-boot_linux/console.log | 333 -
06-build_abe-qemu/console.log | 2388 ++
07-boot_linux/console.log | 11 +
07-check_regression/results.regressions | 2 -
.../console.log | 12 +-
08-check_regression/results.regressions | 2 +
08-update_baseline/results.regressions | 2 -
.../console.log | 18 +-
09-update_baseline/results.regressions | 2 +
console.log | 37812 ++++++++++---------
jenkins/manifest.sh | 19 +-
results | 2 +-
17 files changed, 39903 insertions(+), 35768 deletions(-)
delete mode 100644 06-boot_linux/console.log
create mode 100644 06-build_abe-qemu/console.log
create mode 100644 07-boot_linux/console.log
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (84%)
create mode 100644 08-check_regression/results.regressions
delete mode 100644 08-update_baseline/results.regressions
rename {08-update_baseline => 09-update_baseline}/console.log (76%)
create mode 100644 09-update_baseline/results.regressions
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.