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 717b49c685 binutils-75c1c971842f43157c173728e8465e1ce3c1b838: 18152
discards 400eaa2885 linux-73855109a92c72e41c424aff15c23a289dde032b: 18079
discards 2af607903d binutils-353229bf405113e6ba2fe21f2a691bc63aa94bd8: 18157
new 2913db93c7 linux-dc4c899977350728714d44b6e0d39673f6a97281: 18173
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 (717b49c685)
\
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:
1-reset_artifacts/console.log | 14 +-
2-prepare_abe/console.log | 10 +-
3-build_abe-binutils/console.log | 3639 ++--
4-build_abe-stage1/console.log | 3916 ++--
5-count_linux_objs/console.log | 17932 +++++++++---------
6-check_regression/console.log | 14 +-
7-update_baseline/console.log | 78 +-
console.log | 37931 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 2 +-
trigger-bisect-on-failure | 6 +-
13 files changed, 31820 insertions(+), 31738 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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards d2a07138f5 llvm-8a11e14ef3568455b0e61467a8d578bbb760d3bb: all
new ef5c7a1a8b linux-dc4c899977350728714d44b6e0d39673f6a97281: 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 (d2a07138f5)
\
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:
1-reset_artifacts/console.log | 70 +-
2-build_llvm/console.log | 10121 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 160 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10357 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10380 insertions(+), 10354 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_bmk/gnu-release-aarch64-spec2k6-Os
in repository toolchain/ci/base-artifacts.
discards 2558eefa21 binutils-d43a04899779ad5b7d83ded8e0b3d124ccbac6fb: 0
new b5977aa197 glibc-d09b11cbe57c6434813ead18ff128012230bb614: 0
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 (2558eefa21)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk/gnu-release-aarch64- [...]
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:
.../console.log | 70 +-
{2-prepare_abe => 02-prepare_abe}/console.log | 26 +-
.../console.log | 6030 +-
.../console.log | 8023 +--
.../console.log | 68 +-
.../console.log | 22208 +++----
.../console.log | 22085 ++++---
{8-benchmark => 08-benchmark}/console.log | 44 +-
.../console.log | 211 +-
10-update_baseline/console.log | 213 +-
console.log | 58980 ++++++++++---------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 16 +-
results.csv | 235 +-
results_id | 2 +-
trigger-bisect-on-failure | 6 +-
17 files changed, 59303 insertions(+), 58918 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (67%)
rename {2-prepare_abe => 02-prepare_abe}/console.log (89%)
rename {3-build_abe-binutils => 03-build_abe-binutils}/console.log (63%)
rename {4-build_abe-stage1 => 04-build_abe-stage1}/console.log (59%)
rename {5-build_abe-linux => 05-build_abe-linux}/console.log (80%)
rename {6-build_abe-glibc => 06-build_abe-glibc}/console.log (72%)
rename {7-build_abe-stage2 => 07-build_abe-stage2}/console.log (58%)
rename {8-benchmark => 08-benchmark}/console.log (74%)
rename {9-check_regression => 09-check_regression}/console.log (68%)
--
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-master-aarch64-lts-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 4e8d6c6f9a llvm-7cc0753118473b5a1c646b826819b294a55c302e: 17558
new 457fdac373 llvm-a50489754a60000887c13a04b85c772e867e807a: 17558
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 (4e8d6c6f9a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-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:
1-reset_artifacts/console.log | 70 +-
2-build_llvm/console.log | 10284 +++++++++++++++----------------
3-count_linux_objs/console.log | 2592 ++++----
4-check_regression/console.log | 10 +-
5-update_baseline/console.log | 18 +-
console.log | 12994 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 13068 insertions(+), 12916 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-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 9c157ae925 llvm-61ff0b639cca25747bcbae8bf5a213d702141bc5: 16547
new 173a6f1154 linux-cd984a5be21549273a3f13b52a8b7b84097b32a7: 16547
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 (9c157ae925)
\
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:
1-reset_artifacts/console.log | 14 +-
2-build_llvm/console.log | 9029 +++++++++++++++++----------------
3-count_linux_objs/console.log | 1421 +++---
console.log | 10658 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 10569 insertions(+), 10573 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-master-arm-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 61bd9b9157 llvm-b6c6ab312e9ffa0f1144e3fccc2d25e3afef0e31: all
new f39d85f867 llvm-f82d8924ef7fe20f786d70ee4634be4d5dc508d3: 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 (61bd9b9157)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-l [...]
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:
1-reset_artifacts/console.log | 68 +-
2-build_llvm/console.log | 10272 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 100 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10446 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 10460 insertions(+), 10448 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.