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-defconfig
in repository toolchain/ci/base-artifacts.
discards a6ba0494e gcc-0550105c83f84d4b5e287863e5bf7e445a4d6dc5: all
new b38b0ceb1 linux-755d01d176971569f1231a7cb6b104eedd8f1ed3: 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 (a6ba0494e)
\
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:
1-reset_artifacts/console.log | 16 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3388 +++++++++---------
4-build_abe-stage1/console.log | 3719 ++++++++++---------
5-count_linux_objs/console.log | 136 +-
console.log | 7281 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 7316 insertions(+), 7250 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.
"Maxim Kuvyrkov pushed a change to branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards 5f5a384 [WIP] tcwg_bmk project
new c4be07a [WIP] tcwg_bmk project
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 (5f5a384)
\
N -- N -- N refs/heads/tcwg_bmk (c4be07a)
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:
round-robin.sh | 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.
"Maxim Kuvyrkov pushed a change to branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards 03b1807 [WIP] tcwg_bmk project
new 5f5a384 [WIP] tcwg_bmk project
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 (03b1807)
\
N -- N -- N refs/heads/tcwg_bmk (5f5a384)
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:
jenkins-helpers.sh | 4 ++--
1 file changed, 2 insertions(+), 2 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.
"Maxim Kuvyrkov pushed a change to branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards 26aeb45 [WIP] tcwg_bmk project
new 03b1807 [WIP] tcwg_bmk project
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 (26aeb45)
\
N -- N -- N refs/heads/tcwg_bmk (03b1807)
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:
round-robin.sh | 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-arm-next-allmodconfig
in repository toolchain/ci/base-artifacts.
from 99f48b72f linux-880ee82f0313453ec5a6cb122866ac057263066b: 19157
new 6ff133c83 linux-755d01d176971569f1231a7cb6b104eedd8f1ed3: 19179
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 | 16 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3485 ++++++++--------
4-build_abe-stage1/console.log | 4413 ++++++++++-----------
5-count_linux_objs/console.log | 156 +-
6-check_regression/console.log | 17 +-
7-update_baseline/console.log | 30 +-
console.log | 8077 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 4 +-
12 files changed, 8175 insertions(+), 8041 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.
"Maxim Kuvyrkov pushed a change to branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards 10d8ece [WIP] tcwg_bmk project
new 26aeb45 [WIP] tcwg_bmk project
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 (10d8ece)
\
N -- N -- N refs/heads/tcwg_bmk (26aeb45)
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:
tcwg_bmk-build.sh | 4 +++-
1 file changed, 3 insertions(+), 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/llvm-release-arm-mainline-defconfig
in repository toolchain/ci/base-artifacts.
discards b0c2478a9 llvm-642a1732ef4f120cae6a55725b83bf74c2fa9323: all
new 39a282b47 linux-30bac164aca750892b93eef350439a0562a68647: 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 (b0c2478a9)
\
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 | 68 +-
2-build_llvm/console.log | 10214 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 158 +-
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 | 12 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10439 insertions(+), 10475 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.
"Maxim Kuvyrkov pushed a change to branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards b74e4b6 [WIP] tcwg_bmk project
new 10d8ece [WIP] tcwg_bmk project
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 (b74e4b6)
\
N -- N -- N refs/heads/tcwg_bmk (10d8ece)
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:
docker-run.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.