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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards fac594a15 0: update: llvm-linux: all
new ac7eb5bd0 0: update: llvm-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 (fac594a15)
\
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 | 14 +-
02-build_llvm/console.log | 12610 ++++++++--------
03-build_linux/console.log | 16551 ++++++++++-----------
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 2 +-
06-update_baseline/console.log | 2 +-
console.log | 29181 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
8 files changed, 29197 insertions(+), 29175 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-arm-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c832b8bb2 2: update: llvm-linux: 19240
new c89418ec7 2: update: llvm-linux: 19255
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 (c832b8bb2)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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 | 191 +-
02-build_llvm/console.log | 12550 +++++++++++++--------------
03-build_linux/console.log | 802 +-
05-check_regression/console.log | 24 +-
05-check_regression/results.regressions | 2 +-
06-update_baseline/console.log | 52 +-
06-update_baseline/results.regressions | 2 +-
console.log | 13619 +++++++++++++++---------------
jenkins/manifest.sh | 10 +-
results | 2 +-
10 files changed, 13628 insertions(+), 13626 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_cross/gnu-master-arm-check_cross
in repository toolchain/ci/base-artifacts.
discards c805c28cf 7: update: glibc-29fddfc7dfd6444fa61a256e9a0d0127545e1f2e: 1
discards d5522d70f 6: reset: qemu-4ac4e7281a2dd1ca5158812198c4d2cbacf2ae25: 1
new 5654e5c5f 6: reset: qemu-1b539bd6dbe1459f160e25610ec2fc3388f700e8: 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 (c805c28cf)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_cross/gnu-master-arm-che [...]
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 | 180 +-
02-prepare_abe/console.log | 440 +-
03-build_abe-binutils/console.log | 10930 +-
04-build_abe-stage1/console.log | 20109 ++--
05-build_abe-linux/console.log | 276 +-
06-build_abe-glibc/console.log | 39677 ++++---
07-build_abe-stage2/console.log | 46976 ++++----
08-build_abe-qemu/console.log | 3367 +-
09-build_abe-dejagnu/console.log | 104 +-
10-build_abe-check_gcc/console.log | 30062 +++--
11-check_regression/console.log | 320 +-
11-check_regression/results.regressions | 4 +-
12-update_baseline/console.log | 15610 ++-
12-update_baseline/results.regressions | 4 +-
console.log | 169985 ++++++++++++++---------------
jenkins/manifest.sh | 12 +-
reset-baseline | 0
sumfiles/g++.log.xz | Bin 2282348 -> 2300236 bytes
sumfiles/gcc.log.xz | Bin 2012260 -> 1991400 bytes
sumfiles/gfortran.log.xz | Bin 764984 -> 769996 bytes
sumfiles/libatomic.log.xz | Bin 2228 -> 2236 bytes
sumfiles/libatomic.sum | 2 +-
sumfiles/libgomp.log.xz | Bin 126996 -> 127252 bytes
sumfiles/libgomp.sum | 2 +-
sumfiles/libitm.log.xz | Bin 2608 -> 2604 bytes
sumfiles/libitm.sum | 2 +-
sumfiles/libstdc++.log.xz | Bin 412400 -> 410232 bytes
27 files changed, 165416 insertions(+), 172646 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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 8baf4579b 6: update: binutils-gcc-linux: 19240
new e7ecb99ad 6: update: binutils-gcc-linux: 19248
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 (8baf4579b)
\
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 | 191 +-
02-prepare_abe/console.log | 440 +-
03-build_abe-binutils/console.log | 11727 +++++-----
04-build_abe-stage1/console.log | 20414 ++++++++---------
05-build_linux/console.log | 1931 +-
07-check_regression/console.log | 24 +-
07-check_regression/results.regressions | 20 +-
08-update_baseline/console.log | 144 +-
08-update_baseline/results.regressions | 20 +-
console.log | 34871 +++++++++++++++---------------
jenkins/manifest.sh | 18 +-
results | 2 +-
12 files changed, 35154 insertions(+), 34648 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.