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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards b9ae4df35 gcc-392c53f0f776a4dfe7908f5b3b1377fe78ca77a7: 19163
new 8f4523ee8 binutils-a6c9b4042921847ee52003811383e4b8bf5d5875: 19163
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 (b9ae4df35)
\
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 | 20 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/build-ok | 0
3-build_abe-binutils/console.log | 3651 +-
4-build_abe-stage1/build-ok | 0
4-build_abe-stage1/console.log | 5033 +-
5-count_linux_objs/console.log | 375282 +++++++++++++++++------------------
7-update_baseline/console.log | 3 +-
console.log | 384081 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 6 +-
trigger-bisect-on-failure | 6 +-
14 files changed, 384084 insertions(+), 384018 deletions(-)
delete mode 100644 3-build_abe-binutils/build-ok
delete mode 100644 4-build_abe-stage1/build-ok
--
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-stable-allnoconfig
in repository toolchain/ci/base-artifacts.
discards c72d0e1af llvm-bd9dafecf7b7e311d73dad59fc1b1e913224aaff: all
new 3f36a4448 llvm-67b7e23fa183e2496c27a83b8ba2b85238558487: 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 (c72d0e1af)
\
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 | 140 +-
2-build_llvm/build-ok | 0
2-build_llvm/console.log | 5211 ++++++++++++++++++-------------------
3-count_linux_objs/console.log | 193 +-
console.log | 5544 ++++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 22 +-
results | 4 +-
trigger-bisect-on-failure | 4 +-
10 files changed, 5498 insertions(+), 5624 deletions(-)
delete mode 100644 2-build_llvm/build-ok
--
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-mainline-allmodconfig
in repository toolchain/ci/base-artifacts.
discards 69cbee60b linux-6e693b3ffecb0b478c7050b44a4842854154f715: 19125
new f12c8b34c gcc-ca55c217ce6025bac034f31b8f6510ac097ee69b: 19125
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 (69cbee60b)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]
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 | 20 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/build-ok | 0
3-build_abe-binutils/console.log | 3395 +-
4-build_abe-stage1/build-ok | 0
4-build_abe-stage1/console.log | 4809 +-
5-count_linux_objs/console.log | 368122 +++++++++++++++++------------------
7-update_baseline/console.log | 4 +-
console.log | 375534 ++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 6 +-
trigger-bisect-on-failure | 6 +-
14 files changed, 375994 insertions(+), 375922 deletions(-)
delete mode 100644 3-build_abe-binutils/build-ok
delete mode 100644 4-build_abe-stage1/build-ok
--
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-allmodconfig
in repository toolchain/ci/base-artifacts.
discards fbc3b72a6 linux-2339e91d0e6609e17943a0ab3c3c8c4044760c05: 19127
new 43d4fdb67 llvm-67b7e23fa183e2496c27a83b8ba2b85238558487: 19127
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 (fbc3b72a6)
\
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 | 352 +-
2-build_llvm/build-ok | 0
2-build_llvm/console.log | 10306 +++++++++++++++++-----------------
3-count_linux_objs/console.log | 828 +--
4-check_regression/console.log | 2 +-
5-update_baseline/console.log | 4 +-
console.log | 11686 +++++++++++++++++++--------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 22 +-
results | 4 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 11500 insertions(+), 11714 deletions(-)
delete mode 100644 2-build_llvm/build-ok
--
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 clang.
from feea0777eb [clang] add tests to ExprMutAnalyzer that reproduced a crash [...]
new 77ec61ab8d [NFC] Fix comparison warning issues by MSVC
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:
lib/Sema/SemaDeclAttr.cpp | 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.
"Maxim Kuvyrkov pushed a change to branch maxim
in repository toolchain/jenkins-scripts.
discards a6a7b02 jenkins-helpers.sh: Improve run_step functionality.
new e093e3d jenkins-helpers.sh: Improve run_step functionality.
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 (a6a7b02)
\
N -- N -- N refs/heads/maxim (e093e3d)
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:
--
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 maxim
in repository toolchain/jenkins-scripts.
discards 971e191 jenkins-helpers.sh: Improve run_step functionality.
discards 84a5c74 tcwg_kernel-build.sh: Fix bisection of GCC regressions
discards 929c3a7 tcwg_kernel-bisect: Generalize bisect script for use in tcwg_ [...]
discards 9d3aedd tcwg_kernel*: Correct names of *_rev variables.
discards 4621669 tcwg_kernel-bisect.sh: Re-arrange code.
discards 6d85cae tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
discards 4ec06d5 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop.
discards 9af7bec tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround
discards 391f1ac tcwg_kernel-bisect.sh: Cleanup handling of $good_rev.
discards c80275f tcwg_kernel-bisect.sh: Update reproduction instructions
discards 8de2d5a tcwg_kernel-bisect.sh: Re-arrange code.
discards 96da56c tcwg_kernel-bisect.sh: Put bisect test script into artifacts/
discards bdae8b9 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs
discards d772207 tcwg_kernel-bisect.sh: Simplify handling of artifact directories
discards 82ffe64 tcwg_kernel-bisect.sh: Remove --confirm_failure option
discards bedb5b1 round-robin.sh: Improve comment.
discards a2d204e tcwg_kernel-build.sh: Simplify reproduction logic
discards 498c971 round-robin.sh: Make clone_repo clean repos during bisect builds
discards 462c0bd round-robin.h: Record correct sha1 of base-artifacts/ in manifest
discards 5ab2892 jenkins-helpers: Enable clone_or_update_repo to fetch single branch
discards b98b781 jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
new a61032c jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
new a85440a jenkins-helpers: Enable clone_or_update_repo to fetch single branch
new a87534d round-robin.h: Record correct sha1 of base-artifacts/ in manifest
new 0c835eb round-robin.sh: Make clone_repo clean repos during bisect builds
new 0fc62db tcwg_kernel-build.sh: Simplify reproduction logic
new 22b7df0 round-robin.sh: Improve comment.
new 73d563e tcwg_kernel-bisect.sh: Remove --confirm_failure option
new 8a88980 tcwg_kernel-bisect.sh: Simplify handling of artifact directories
new c29f90f tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs
new 845244b tcwg_kernel-bisect.sh: Put bisect test script into artifacts/
new 8c175bd tcwg_kernel-bisect.sh: Re-arrange code.
new f6b6c04 tcwg_kernel-bisect.sh: Update reproduction instructions
new 1c7b10c tcwg_kernel-bisect.sh: Cleanup handling of $good_rev.
new e7e9db0 tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround
new 2c05acb tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop.
new df72553 tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
new c5928d0 tcwg_kernel-bisect.sh: Re-arrange code.
new 027040f tcwg_kernel*: Correct names of *_rev variables.
new 0b7190e tcwg_kernel-bisect: Generalize bisect script for use in tcwg_ [...]
new 6f4fd92 tcwg_kernel-build.sh: Fix bisection of GCC regressions
new a6a7b02 jenkins-helpers.sh: Improve run_step functionality.
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 (971e191)
\
N -- N -- N refs/heads/maxim (a6a7b02)
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 21 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 +---
round-robin.sh | 4 ++--
2 files changed, 3 insertions(+), 5 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/ci/base-artifacts.
discards 07ed31b46 binutils-6b53149a41ae1e8950063e1151c3d10011b08f9b: all
new 4720bc3ae linux-49a57857aeea06ca831043acbb0fa5e0f50602fd: 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 (07ed31b46)
\
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 | 20 +-
2-prepare_abe/console.log | 4 +-
3-build_abe-binutils/build-ok | 0
3-build_abe-binutils/console.log | 3667 +++++++++--------
4-build_abe-stage1/build-ok | 0
4-build_abe-stage1/console.log | 3979 ++++++++++---------
5-count_linux_objs/console.log | 193 +-
5-count_linux_objs/kernel.release | 2 +-
console.log | 7909 ++++++++++++++++++-------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 6 +-
trigger-bisect-on-failure | 6 +-
14 files changed, 7810 insertions(+), 7992 deletions(-)
delete mode 100644 3-build_abe-binutils/build-ok
delete mode 100644 4-build_abe-stage1/build-ok
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.