This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 50c4a518122 MAINTAINERS: add myself.
new 1425cbaac1a 2019-01-22 Richard Biener <rguenther(a)suse.de>
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:
gcc/ChangeLog | 8 ++++++++
gcc/tree-vect-loop.c | 14 +++++++++-----
gcc/tree-vect-stmts.c | 11 +++++++----
3 files changed, 24 insertions(+), 9 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 2325d05b1 binutils-be6d4f74c77c6f521afc873d226480e001cb99c2: all
new 308bbd3b1 gcc-1425cbaac1ac200627dc147b7dc46734b8d50308: 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 (2325d05b1)
\
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 | 70 +-
2-prepare_abe/console.log | 26 +-
3-build_abe-binutils/console.log | 6225 +++++-----
4-build_abe-stage1/console.log | 13206 ++++++++++-----------
5-count_linux_objs/console.log | 3637 +++---
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 4 +-
console.log | 23338 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
trigger-bisect-on-failure | 6 +-
12 files changed, 23293 insertions(+), 23237 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 maxim
in repository toolchain/jenkins-scripts.
at 148a356 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
This branch includes the following new commits:
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 f26158b tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
new 9008bee tcwg_kernel-bisect.sh: Re-arrange code.
new 11f9dcb tcwg_kernel*: Correct names of *_rev variables.
new 497d0b6 tcwg_kernel-bisect: Generalize bisect script for use in tcwg_ [...]
new 3269f95 tcwg_kernel-build.sh: Fix bisection of GCC regressions
new 60a6d74 jenkins-helpers.sh: Improve run_step functionality.
new 2068396 tcwg_kernel-bisect.sh: Fetch build-parameters.sh in reproduct [...]
new e0b5b89 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new 148a356 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
The 24 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.
--
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 3148df5 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
discards bc4325f tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new e0b5b89 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new 148a356 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
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 (3148df5)
\
N -- N -- N refs/heads/maxim (148a356)
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 2 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 | 6 +++---
2 files changed, 5 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.
unknown user pushed a change to branch master
in repository zorg.
from 697ad85b Only add one property WithProperties invocation
new 449cbc0b [Fuchsia] Always clean-up the SDK directory
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:
zorg/buildbot/builders/FuchsiaBuilder.py | 7 +++----
1 file changed, 3 insertions(+), 4 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 a535cd1e4 binutils-111f47f3e4b685acc2378e46d0221e562c608ffc: 16548
new 4ee939c5f linux-48b161983ae5266ffa42f0ccaf7224eaeda38e59: 16548
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 (a535cd1e4)
\
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 | 76 +-
2-prepare_abe/console.log | 30 +-
3-build_abe-binutils/build-ok | 0
3-build_abe-binutils/console.log | 6157 +++--
4-build_abe-stage1/build-ok | 0
4-build_abe-stage1/console.log | 9303 ++++----
5-count_linux_objs/console.log | 29923 ++++++++++++------------
6-check_regression/console.log | 2 +-
7-update_baseline/console.log | 11 +-
console.log | 45432 +++++++++++++++++++------------------
distance-to-baseline | 2 +-
jenkins/build-name | 2 +-
jenkins/manifest.sh | 12 +-
results | 6 +-
trigger-bisect-on-failure | 6 +-
15 files changed, 45517 insertions(+), 45445 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.
"Maxim Kuvyrkov pushed a change to branch maxim
in repository toolchain/jenkins-scripts.
discards 338961e tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
discards 5d3bb96 tcwg_kernel-bisect.sh: Fetch build-parameters.sh in reproduct [...]
discards e093e3d jenkins-helpers.sh: Improve run_step functionality.
discards 6f4fd92 tcwg_kernel-build.sh: Fix bisection of GCC regressions
discards 0b7190e tcwg_kernel-bisect: Generalize bisect script for use in tcwg_ [...]
discards 027040f tcwg_kernel*: Correct names of *_rev variables.
discards c5928d0 tcwg_kernel-bisect.sh: Re-arrange code.
discards df72553 tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
new f26158b tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
new 9008bee tcwg_kernel-bisect.sh: Re-arrange code.
new 11f9dcb tcwg_kernel*: Correct names of *_rev variables.
new 497d0b6 tcwg_kernel-bisect: Generalize bisect script for use in tcwg_ [...]
new 3269f95 tcwg_kernel-build.sh: Fix bisection of GCC regressions
new 60a6d74 jenkins-helpers.sh: Improve run_step functionality.
new 2068396 tcwg_kernel-bisect.sh: Fetch build-parameters.sh in reproduct [...]
new bc4325f tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new 3148df5 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
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 (338961e)
\
N -- N -- N refs/heads/maxim (3148df5)
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 9 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 | 5 +++++
tcwg_kernel-bisect.sh | 37 ++++++++++++++++++++++++++++++-------
2 files changed, 35 insertions(+), 7 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.