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_LTO
in repository toolchain/ci/gcc.
from c8325216a3d Backport from mainline 2018-10-15 Bin Cheng <bin.cheng@ [...]
new 6142f179ac2 Daily bump.
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:
gcc/DATESTAMP | 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_bmk/gnu-release-aarch64-spec2k6-Os_LTO
in repository toolchain/ci/base-artifacts.
discards 301dbde7ce gcc-c8325216a3d4f5f871020365c87dc1346024c766: 0
new 71dcc378ff gcc-6142f179ac2e366e194efd6409e01d624d034ed1: 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 (301dbde7ce)
\
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 | 34 +-
{2-prepare_abe => 02-prepare_abe}/console.log | 4 +-
.../console.log | 3593 ++-
.../console.log | 4208 ++--
.../console.log | 24 +-
.../console.log | 1263 +-
.../console.log | 13584 ++++++-----
{8-benchmark => 08-benchmark}/console.log | 36 +-
.../console.log | 194 +-
10-update_baseline/console.log | 194 +-
console.log | 22974 ++++++++++---------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 16 +-
results.csv | 236 +-
results_id | 2 +-
trigger-bisect-on-failure | 4 +-
17 files changed, 23341 insertions(+), 23029 deletions(-)
rename {1-reset_artifacts => 01-reset_artifacts}/console.log (86%)
rename {2-prepare_abe => 02-prepare_abe}/console.log (99%)
rename {3-build_abe-binutils => 03-build_abe-binutils}/console.log (95%)
rename {4-build_abe-stage1 => 04-build_abe-stage1}/console.log (95%)
rename {5-build_abe-linux => 05-build_abe-linux}/console.log (94%)
rename {6-build_abe-glibc => 06-build_abe-glibc}/console.log (99%)
rename {7-build_abe-stage2 => 07-build_abe-stage2}/console.log (98%)
rename {8-benchmark => 08-benchmark}/console.log (81%)
rename {9-check_regression => 09-check_regression}/console.log (73%)
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards f95c627dca llvm-7539fa2c2d1fe54fbb7f9e01ea07ebcec012a144: all
new 556898bf70 llvm-a50489754a60000887c13a04b85c772e867e807a: 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 (f95c627dca)
\
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 | 68 +-
2-build_llvm/console.log | 10291 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 75 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10440 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 10496 insertions(+), 10400 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-aarch64-next-defconfig
in repository toolchain/ci/base-artifacts.
discards 441397d4ae llvm-743ba66f93dc14c3f78fa2c3d29865c41e89b5a1: 5141
new 48625c2651 linux-dc4c899977350728714d44b6e0d39673f6a97281: 5147
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 (441397d4ae)
\
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 | 68 +-
2-build_llvm/console.log | 10219 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 305 +-
4-check_regression/console.log | 10 +-
5-update_baseline/console.log | 36 +-
console.log | 10638 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
results | 2 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 10545 insertions(+), 10753 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-aarch64-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 688893dcbd llvm-743ba66f93dc14c3f78fa2c3d29865c41e89b5a1: all
new 12dc2a071f 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 (688893dcbd)
\
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 | 68 +-
2-build_llvm/console.log | 10231 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 241 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10546 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10454 insertions(+), 10658 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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 46b443061f llvm-8a11e14ef3568455b0e61467a8d578bbb760d3bb: all
new 60ec06ebe5 llvm-b96362ffa9ceecf2256373f2e86a3e62780c599f: 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 (46b443061f)
\
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 | 10204 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 65 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10345 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 10352 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_kernel/llvm-master-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 18467fa63d llvm-b3ccc5550d985395a7b43cfdd93bc400b332dcdb: 16547
new 31f5a3f9d2 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 (18467fa63d)
\
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 | 68 +-
2-build_llvm/console.log | 10195 +++++++++++++++++-----------------
3-count_linux_objs/console.log | 1309 ++---
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 11580 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 11585 insertions(+), 11593 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.