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-mainline-allmodconfig
in repository toolchain/binutils-gdb.
from 109f0429e0 Automatic date update in version.in
adds fdc1fe728f Automatic date update in version.in
No new revisions were added by this update.
Summary of changes:
bfd/version.h | 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-aarch64-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 1bfdbcef4 linux-903b77c631673eeec9e9114e9524171cdf9a2646: all
new af2a1693e binutils-fdc1fe728f15917f731ab1fec3520e8548c7ad04: 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 (1bfdbcef4)
\
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 | 126 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6548 ++++++++--------
4-build_abe-stage1/console.log | 8356 ++++++++++----------
5-count_linux_objs/console.log | 286 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 15384 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 15137 insertions(+), 15613 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-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards b3cb9766a linux-903b77c631673eeec9e9114e9524171cdf9a2646: all
new e09fc0977 gcc-1f957e932ebf05167137eb6e61b728aefcbfb11f: 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 (b3cb9766a)
\
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 | 48 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3574 ++---
4-build_abe-stage1/console.log | 5120 +++---
5-count_linux_objs/console.log | 22228 +++++++++++++-------------
console.log | 31110 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 31088 insertions(+), 31016 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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards 5dd49ad10 llvm-58e92dce7b74cb42178ca4516e82c3723b3a6cb8: 17398
new 0236d22b8 llvm-30ffad93013adfb4bce6e6fd0268b39c4aad903b: 17398
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 (5dd49ad10)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-master-arm-n [...]
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 | 84 +-
2-build_llvm/console.log | 10153 +++++++++++++++++++------------------
3-count_linux_objs/console.log | 331 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10574 ++++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 6 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 10641 insertions(+), 10521 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-release-aarch64-lts-allyesconfig
in repository toolchain/gcc.
from 3637548fdd8 poly_int: get_inner_reference & co.: fix known_eq typo/bug
adds ab5ff873eda Daily bump.
No new revisions were added by this update.
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_kernel/gnu-release-aarch64-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards ec6b33470 binutils-fdc1fe728f15917f731ab1fec3520e8548c7ad04: all
new a3c0d496a gcc-ab5ff873eda78cce583dd567b5f3ac755f1076d6: 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 (ec6b33470)
\
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 | 62 +-
2-prepare_abe/console.log | 22 +-
3-build_abe-binutils/console.log | 6679 ++++++++--------
4-build_abe-stage1/console.log | 8182 ++++++++++----------
5-count_linux_objs/console.log | 102 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 15083 ++++++++++++++++++-------------------
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 15041 insertions(+), 15111 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-aarch64-next-defconfig
in repository toolchain/ci/base-artifacts.
discards f3d058994 gcc-2f86af0adfc315ed006db36540ec9f37c74fd9b9: all
new 14736ac83 binutils-64c45143db4c550e19763edf97ca3441c78f9a05: 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 (f3d058994)
\
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 | 91 +-
2-prepare_abe/console.log | 22 +-
3-build_abe-binutils/console.log | 6626 ++++----
4-build_abe-stage1/console.log | 9489 ++++++-----
5-count_linux_objs/console.log | 15947 +++++++++---------
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 32499 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 32328 insertions(+), 32370 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-release-aarch64-mainline-allyesconfig
in repository toolchain/gcc.
from 3637548fdd8 poly_int: get_inner_reference & co.: fix known_eq typo/bug
adds ab5ff873eda Daily bump.
No new revisions were added by this update.
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_kernel/gnu-release-aarch64-mainline-allyesconfig
in repository toolchain/ci/base-artifacts.
discards ce8273381 linux-903b77c631673eeec9e9114e9524171cdf9a2646: all
new 0b4fcebf1 gcc-ab5ff873eda78cce583dd567b5f3ac755f1076d6: 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 (ce8273381)
\
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 | 86 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3615 ++++++++--------
4-build_abe-stage1/console.log | 4135 +++++++++----------
5-count_linux_objs/console.log | 589 +--
console.log | 8437 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 8566 insertions(+), 8320 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 41579ce0e linux-903b77c631673eeec9e9114e9524171cdf9a2646: all
new b3da6c98f llvm-30ffad93013adfb4bce6e6fd0268b39c4aad903b: 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 (41579ce0e)
\
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 | 288 +-
2-build_llvm/console.log | 8917 +++++++++++++++++++-------------------
3-count_linux_objs/console.log | 226 +-
console.log | 9399 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9291 insertions(+), 9557 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-defconfig
in repository toolchain/ci/base-artifacts.
discards d9cc77b88 binutils-64c45143db4c550e19763edf97ca3441c78f9a05: all
new 38b360875 gcc-1f957e932ebf05167137eb6e61b728aefcbfb11f: 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 (d9cc77b88)
\
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 | 90 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3578 ++-
4-build_abe-stage1/console.log | 4890 ++---
5-count_linux_objs/console.log | 33772 +++++++++++++++--------------
console.log | 43200 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 42712 insertions(+), 42840 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 d24fae0b2 llvm-4e1bfe7ac357046b10fcb1305816913f7343e490: 16
new 329bb372c linux-d2dd9f1593dc4d5ceb5cf4a973ed2c6e3a49d799: 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 (d24fae0b2)
\
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 | 324 +-
2-build_llvm/console.log | 10127 ++++++++++++++++++------------------
3-count_linux_objs/console.log | 250 +-
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 10707 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 8 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 10645 insertions(+), 10787 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-lts-allyesconfig
in repository toolchain/ci/base-artifacts.
discards c9ed8dd3a gcc-640647d4a9e352004a9db35a8d062311c5aa976f: all
new d3be021b2 linux-d2dd9f1593dc4d5ceb5cf4a973ed2c6e3a49d799: 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 (c9ed8dd3a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-lt [...]
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 +-
3-build_abe-binutils/console.log | 3531 +++--
4-build_abe-stage1/console.log | 5303 +++----
5-count_linux_objs/console.log | 31758 +++++++++++++++++++------------------
console.log | 30896 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 6 +-
trigger-bisect-on-failure | 6 +-
9 files changed, 35766 insertions(+), 35778 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-release-arm-lts-allnoconfig
in repository toolchain/gcc.
from 3637548fdd8 poly_int: get_inner_reference & co.: fix known_eq typo/bug
adds ab5ff873eda Daily bump.
No new revisions were added by this update.
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_kernel/gnu-release-arm-lts-allnoconfig
in repository toolchain/ci/base-artifacts.
discards ced00dd73 binutils-fdc1fe728f15917f731ab1fec3520e8548c7ad04: all
new 17d1d1e57 gcc-ab5ff873eda78cce583dd567b5f3ac755f1076d6: 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 (ced00dd73)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-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 | 45 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6315 +++++++------
4-build_abe-stage1/console.log | 11946 ++++++++++++------------
5-count_linux_objs/console.log | 59 +-
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 18395 ++++++++++++++++++-------------------
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 18396 insertions(+), 18414 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 cf608f761 linux-00c569b567c7f1f0da6162868fd02a9f29411805: all
new cccece8ea llvm-30ffad93013adfb4bce6e6fd0268b39c4aad903b: 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 (cf608f761)
\
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 | 295 +-
2-build_llvm/console.log | 8905 ++++++++++++++++++-------------------
3-count_linux_objs/console.log | 221 +-
console.log | 9443 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
8 files changed, 9639 insertions(+), 9245 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.