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 45c66d9b9 1: reset: linux-qemu: 19364
discards a5f283b37 0: update: binutils-gcc-linux-qemu: all
new 42552d33d 0: update: binutils-gcc-linux-qemu: 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 (45c66d9b9)
\
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 | 132 +-
02-prepare_abe/console.log | 446 +-
03-build_abe-binutils/console.log | 11497 ++++++------
04-build_abe-stage1/console.log | 13770 +++++++-------
05-build_linux/console.log | 517 +-
06-build_abe-qemu/console.log | 2408 +++
07-boot_linux/console.log | 13 +
08-check_regression/console.log | 145 +-
08-check_regression/results.regressions | 7 +-
08-check_regression/trigger-build-linux | 5 -
08-check_regression/trigger-build-qemu | 5 -
09-update_baseline/console.log | 47 +-
09-update_baseline/results.regressions | 7 +-
console.log | 29041 ++++++++++++++++--------------
jenkins/manifest.sh | 21 +-
reset-baseline | 0
results | 11 +-
17 files changed, 31921 insertions(+), 26151 deletions(-)
create mode 100644 06-build_abe-qemu/console.log
create mode 100644 07-boot_linux/console.log
delete mode 100644 08-check_regression/trigger-build-linux
delete mode 100644 08-check_regression/trigger-build-qemu
delete 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-release-aarch64-mainline-allyesconfig
in repository toolchain/ci/binutils-gdb.
from 6828c0c676 Automatic date update in version.in
adds 4611585313 Automatic date update in version.in
adds e7f46bfe0b Automatic date update in version.in
adds 23f34add74 Automatic date update in version.in
adds 85d6c75350 Automatic date update in version.in
adds 10a9da658e Automatic date update in version.in
adds 8f9eec44b3 Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
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-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards f9b173214 2: update: linux-e37b12e4bb21e7c81732370b0a2b34bd196f380b: 19364
new 8ab368c11 2: update: binutils-gcc-qemu: 19364
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 (f9b173214)
\
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 | 130 +-
02-prepare_abe/console.log | 174 +-
03-build_abe-binutils/console.log | 10932 +++++++------
04-build_abe-stage1/console.log | 13724 ++++++++--------
05-build_linux/console.log | 584 +-
08-check_regression/console.log | 8 +-
08-check_regression/results.regressions | 12 +-
09-update_baseline/console.log | 64 +-
09-update_baseline/results.regressions | 12 +-
console.log | 25654 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
11 files changed, 26152 insertions(+), 25160 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-master-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 68e09cbb4 4: update: binutils-gcc-linux-qemu: 22
new 34d8f5c06 4: update: binutils-gcc-linux-qemu: 22
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 (68e09cbb4)
\
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 | 128 +-
02-prepare_abe/console.log | 410 +-
03-build_abe-binutils/console.log | 10393 ++++---
04-build_abe-stage1/console.log | 20816 +++++++-------
05-build_linux/console.log | 13901 +++++----
08-check_regression/console.log | 2 +-
08-check_regression/results.regressions | 20 +-
09-update_baseline/console.log | 94 +-
09-update_baseline/results.regressions | 20 +-
console.log | 45840 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
11 files changed, 45791 insertions(+), 45851 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_gnu/gnu-master-aarch64-check_binutils
in repository toolchain/ci/base-artifacts.
discards c60b43595 0: update: binutils-904cb749cf4ed4e26aec6a9f471497f7534f8cc3: 1
new cbb782a28 0: update: binutils-9423103f5486c7fc4666f2a35becff9196fbc632: 1
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 (c60b43595)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu/gnu-master-aarch64-c [...]
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 | 95 +-
02-prepare_abe/console.log | 442 +-
03-build_abe-binutils/console.log | 13653 +++++++++++----------
04-build_abe-check_binutils/console.log | 5104 ++++----
05-check_regression/console.log | 142 +-
05-check_regression/results.regressions | 4 +-
06-update_baseline/console.log | 278 +-
06-update_baseline/results.regressions | 4 +-
console.log | 19714 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
sumfiles/binutils.log.xz | Bin 37232 -> 37188 bytes
sumfiles/binutils.sum | 2 +-
sumfiles/gas.log.xz | Bin 71376 -> 71380 bytes
sumfiles/gas.sum | 4 +-
sumfiles/ld.log.xz | Bin 106240 -> 106228 bytes
sumfiles/ld.sum | 4 +-
16 files changed, 19712 insertions(+), 19744 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.