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-master-arm-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 808c2840 0: update: llvm-linux: 18628
new 1b633aea 0: update: llvm-linux: 18628
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 (808c2840)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-m [...]
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 | 12926 ++++++++++++++--------------
03-build_linux/console.log | 746 +-
05-check_regression/console.log | 2 +-
05-check_regression/results.regressions | 2 +-
06-update_baseline/console.log | 2 +-
06-update_baseline/results.regressions | 2 +-
console.log | 13690 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
9 files changed, 13713 insertions(+), 13685 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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 6d6bae15 0: update: llvm-eaae6dfc545000e335e6f89abb9c78818383d7ad: all
new 05facd56 0: reset: linux-3c40cdb0e93ec166f1fa4fee1eb62d45b5451515: 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 (6d6bae15)
\
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 | 113 +-
02-build_llvm/console.log | 12505 ++++++++++++++++++-----------------
03-build_linux/console.log | 641 +-
04-boot_linux/console.log | 2 +-
05-check_regression/console.log | 14 +-
06-update_baseline/console.log | 24 +-
console.log | 13299 +++++++++++++++++++-------------------
jenkins/manifest.sh | 10 +-
reset-baseline | 0
results | 2 +-
10 files changed, 13244 insertions(+), 13366 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_bmk_tk1/gnu-master-arm-spec2k6-O3
in repository toolchain/ci/base-artifacts.
discards 0534f5aa 2: update: binutils-gcc-glibc: 1
new 3ac03898 2: reset: : 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 (0534f5aa)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_tk1/gnu-master-arm-s [...]
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 | 88 +-
02-prepare_abe/console.log | 442 +-
03-build_abe-binutils/console.log | 11267 ++-
04-build_abe-stage1/console.log | 20246 +++--
05-build_abe-linux/console.log | 164 +-
06-build_abe-glibc/console.log | 38555 ++++-----
07-build_abe-stage2/console.log | 45271 +++++-----
09-benchmark--O3_marm/benchmark-start.log | 2 +-
09-benchmark--O3_marm/benchmark.log | 46 +-
09-benchmark--O3_marm/console.log | 378 +-
10-check_regression/console.log | 3642 +-
10-check_regression/results-0.csv | 3184 +-
10-check_regression/results-1.csv | 3125 +-
10-check_regression/results-brief.csv | 58 +-
10-check_regression/results-compare.csv | 10 +-
10-check_regression/results-full.csv | 3408 +-
10-check_regression/results.csv | 240 +-
10-check_regression/results.log | 3808 +-
11-update_baseline/console.log | 4422 +-
11-update_baseline/results-1.csv | 3125 +-
11-update_baseline/results-brief.csv | 56 +-
11-update_baseline/results-compare.csv | 10 +-
11-update_baseline/results-full.csv | 3120 +-
11-update_baseline/results.csv | 236 +-
11-update_baseline/results.log | 2676 +-
console.log | 125299 +++++++++++++--------------
jenkins/manifest.sh | 13 +-
reset-baseline | 0
results_id | 2 +-
29 files changed, 135346 insertions(+), 137547 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-aarch64-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 613676c1 0: update: binutils-gcc-linux: boot
new 40ff35e4 0: update: linux-79dede78c0573618e3137d3d8cbf78c84e25fabd: 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 (613676c1)
\
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 | 130 +-
02-prepare_abe/console.log | 414 +-
03-build_abe-binutils/console.log | 11528 +++++------
04-build_abe-stage1/console.log | 15703 +++++++-------
05-build_linux/console.log | 5573 ++---
07-check_regression/console.log | 2 +-
07-check_regression/results.regressions | 2 +-
08-update_baseline/console.log | 2 +-
08-update_baseline/results.regressions | 2 +-
console.log | 33354 +++++++++++++++---------------
jenkins/manifest.sh | 14 +-
11 files changed, 32777 insertions(+), 33947 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.