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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 38e80b3f 2: update: binutils-gcc-linux: 16047
new fdcc8a15 2: update: binutils-gcc-linux: 16047
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 (38e80b3f)
\
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 | 175 +-
02-prepare_abe/console.log | 282 +-
03-build_abe-binutils/console.log | 11791 +++----
04-build_abe-stage1/console.log | 15992 ++++-----
05-build_linux/console.log | 6407 ++--
07-check_regression/results.regressions | 11 -
.../console.log | 2 +-
08-check_regression/results.regressions | 11 +
08-update_baseline/results.regressions | 11 -
.../console.log | 16 +-
09-update_baseline/results.regressions | 11 +
console.log | 34665 ++++++++++---------
jenkins/manifest.sh | 18 +-
13 files changed, 34712 insertions(+), 34680 deletions(-)
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (98%)
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 (93%)
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/gnu-release-aarch64-stable-allmodconfig
in repository toolchain/ci/base-artifacts.
discards bcfd2f34 0: update: binutils-gcc-linux: all
new abe4f577 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 (bcfd2f34)
\
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:
01-reset_artifacts/console.log | 238 +-
02-prepare_abe/console.log | 446 +-
03-build_abe-binutils/console.log | 11790 ++++----
04-build_abe-stage1/console.log | 13889 ++++-----
05-build_linux/console.log | 805 +-
06-boot_linux/console.log | 333 -
06-build_abe-qemu/console.log | 2408 ++
07-boot_linux/console.log | 11 +
07-check_regression/results.regressions | 2 -
.../console.log | 2 +-
08-check_regression/results.regressions | 2 +
08-update_baseline/results.regressions | 2 -
.../console.log | 10 +-
09-update_baseline/results.regressions | 2 +
console.log | 29890 ++++++++++---------
jenkins/manifest.sh | 15 +-
16 files changed, 32014 insertions(+), 27831 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 (98%)
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 (89%)
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/gnu-master-aarch64-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards e4a13a3b 4: update: binutils-gcc-linux: 6380
discards 21801709 3: reset: linux-6e7b64b9dd6d96537d816ea07ec26b7dedd397b9: 6380
discards f0e74f5e 2: update: binutils-gcc: 6381
new bdac6a50 2: update: binutils-gcc-linux: 6384
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 (e4a13a3b)
\
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 | 220 +-
02-prepare_abe/console.log | 280 +-
03-build_abe-binutils/console.log | 11646 ++++----
04-build_abe-stage1/console.log | 15992 +++++-----
05-build_linux/console.log | 782 +-
07-check_regression/results.regressions | 7 -
.../console.log | 22 +-
08-check_regression/results.regressions | 7 +
08-update_baseline/console.log | 107 -
08-update_baseline/results.regressions | 7 -
09-update_baseline/console.log | 171 +
09-update_baseline/results.regressions | 7 +
console.log | 29082 ++++++++++---------
jenkins/manifest.sh | 22 +-
results | 2 +-
15 files changed, 29258 insertions(+), 29096 deletions(-)
delete mode 100644 07-check_regression/results.regressions
rename {07-check_regression => 08-check_regression}/console.log (75%)
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-defconfig
in repository toolchain/ci/base-artifacts.
discards ea750a55 0: update: llvm-linux: boot
new 64cf7814 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 (ea750a55)
\
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 | 184 +-
02-build_llvm/console.log | 6416 -------
02-prepare_abe/console.log | 254 +
03-build_linux/console.log | 1024 --
03-build_llvm/console.log | 6416 +++++++
04-boot_linux/console.log | 534 -
04-build_linux/console.log | 1025 ++
05-build_abe-qemu/console.log | 2407 +++
06-boot_linux/console.log | 212 +
.../console.log | 12 +-
.../results.regressions | 0
.../console.log | 18 +-
.../results.regressions | 0
console.log | 18254 +++++++++++--------
jenkins/manifest.sh | 11 +-
15 files changed, 20725 insertions(+), 16042 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 (76%)
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.