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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 647cb9205 binutils-0275cea0c3fb3a0dac95bf048e123ca1c7d6192c: all
new 8cc08abd9 gcc-4dfb886147d3e37b40bd0a20cb56860ab925554d: 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 (647cb9205)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-s [...]
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 | 56 +-
2-prepare_abe/console.log | 6 +-
3-build_abe-binutils/console.log | 3581 ++++++++-------
4-build_abe-stage1/console.log | 5056 ++++++++++-----------
5-count_linux_objs/console.log | 63 +-
5-count_linux_objs/kernel.release | 1 +
console.log | 8758 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 8797 insertions(+), 8744 deletions(-)
create mode 100644 5-count_linux_objs/kernel.release
--
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-next-allyesconfig
in repository toolchain/ci/binutils-gdb.
from 8f41e0d37a Automatic date update in version.in
adds afef1fb8f3 Automatic date update in version.in
adds 0275cea0c3 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-next-allyesconfig
in repository toolchain/ci/base-artifacts.
discards a19425864 gcc-4dfb886147d3e37b40bd0a20cb56860ab925554d: all
new d1ed92ecc binutils-0275cea0c3fb3a0dac95bf048e123ca1c7d6192c: 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 (a19425864)
\
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 | 92 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3748 +++++++++--------
4-build_abe-stage1/console.log | 4334 +++++++++----------
5-count_linux_objs/console.log | 187 +-
5-count_linux_objs/kernel.release | 1 +
console.log | 8429 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 8377 insertions(+), 8438 deletions(-)
create mode 100644 5-count_linux_objs/kernel.release
--
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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards eb3f0023c linux-7939f8beecf1cfb10d255be65bfbd3793fae82a1: 18070
new 00d7beefc llvm-fa970076109609e1536d5ea84183980b69324f60: 18070
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 (eb3f0023c)
\
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 | 148 +-
2-build_llvm/console.log | 10292 +++++++++++++++----------------
3-count_linux_objs/console.log | 1435 ++---
3-count_linux_objs/kernel.release | 1 +
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 12 +-
console.log | 11873 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 11879 insertions(+), 11904 deletions(-)
create mode 100644 3-count_linux_objs/kernel.release
--
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-allnoconfig
in repository toolchain/ci/base-artifacts.
discards 3f25b125f binutils-338c923d26fa86f695fcdc4b659a5f0772768093: all
new 72c32169e gcc-2c099ba4fa7201376c51b7c146e2f65619d9d840: 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 (3f25b125f)
\
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 | 39 +-
2-prepare_abe/console.log | 6 +-
3-build_abe-binutils/console.log | 3654 +++++++++--------
4-build_abe-stage1/console.log | 4410 ++++++++++----------
5-count_linux_objs/console.log | 105 +-
console.log | 8226 +++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
10 files changed, 8162 insertions(+), 8298 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-defconfig
in repository toolchain/ci/base-artifacts.
discards 65757db2b gcc-0ca47588bd2e38bbfa427503968e08a6b8ab3166: all
new ea6a68129 linux-47bfa6d9dc8c060bf56554a465c9031e286d2f80: 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 (65757db2b)
\
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 | 62 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/console.log | 3766 +++---
4-build_abe-stage1/console.log | 4522 ++++---
5-count_linux_objs/console.log | 14627 +++++++++++------------
5-count_linux_objs/kernel.release | 1 +
console.log | 22993 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 10 +-
trigger-bisect-on-failure | 6 +-
11 files changed, 22953 insertions(+), 23042 deletions(-)
create mode 100644 5-count_linux_objs/kernel.release
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.