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-lts-defconfig
in repository toolchain/ci/base-artifacts.
discards 1542e99f5 binutils-c3cc81413c89eab69ac950ce53f91c51cc100349: all
new be4033c53 gcc-7a0b9b3f488d0a92a55ac974d7ae76e70a528f7a: 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 (1542e99f5)
\
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 | 54 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6562 ++++++++--------
4-build_abe-stage1/console.log | 8858 ++++++++++-----------
5-count_linux_objs/console.log | 169 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 15685 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 15750 insertions(+), 15632 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 9d6e23ccd llvm-bd8b20097f5003d7d8988a6d6314026bcce91b50: all
new 9c05330e4 linux-24737fa6bcf1d7ffb71ceb78d7a7c275cb7e1d13: 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 (9d6e23ccd)
\
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 | 74 +-
2-build_llvm/console.log | 9158 +++++++++++++++--------------
3-count_linux_objs/console.log | 3098 +++++-----
console.log | 12272 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 12341 insertions(+), 12281 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-mainline-allnoconfig
in repository toolchain/ci/base-artifacts.
discards b8897567a linux-7b55851367136b1efd84d98fea81ba57a98304cf: all
new 5d17e426a llvm-a6339d93fef27ad77231a7542c3dfa989d930255: 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 (b8897567a)
\
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:
1-reset_artifacts/console.log | 40 +-
2-build_llvm/console.log | 10224 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 225 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10495 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10553 insertions(+), 10459 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.
unknown user pushed a change to branch master
in repository binutils-gdb.
from 669e09f609 NEWS: Move changed commands description to Changed commands [...]
new a08da33eb3 Merge from gcc: use "cannot" instead of "can not" in libiber [...]
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:
include/ChangeLog | 8 ++++++++
include/libiberty.h | 4 ++--
include/plugin-api.h | 2 +-
libiberty/ChangeLog | 9 +++++++++
libiberty/cp-demangle.c | 4 ++--
libiberty/floatformat.c | 2 +-
libiberty/strerror.c | 2 +-
7 files changed, 24 insertions(+), 7 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/gnu-master-arm-next-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 5577fa540 gcc-2f95b84b93eb0f0e351009ccdd2fb90b40b1a746: all
new 12dc74748 binutils-448b8ca86519cce1216c9db5f0236604a6a33320: 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 (5577fa540)
\
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:
1-reset_artifacts/console.log | 62 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3503 ++++----
4-build_abe-stage1/console.log | 5110 ++++++------
5-count_linux_objs/console.log | 7763 +++++++++---------
console.log | 16248 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 16518 insertions(+), 16194 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-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 6329cc8c1 llvm-4946dbe2747e9df573aa59b732135bd10b43fc87: 16
new 32ed680aa linux-24737fa6bcf1d7ffb71ceb78d7a7c275cb7e1d13: 16
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 (6329cc8c1)
\
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 | 74 +-
2-build_llvm/console.log | 10205 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 222 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10507 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10444 insertions(+), 10590 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.