This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/50/29850/2
in repository toolchain/jenkins-scripts.
discards 462166953 tcwg_kernel-bisect.sh: Re-arrange code.
discards 6d85caef7 tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
discards 4ec06d572 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop.
discards 9af7bec1f tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround
discards 391f1ac72 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev.
discards c80275f2d tcwg_kernel-bisect.sh: Update reproduction instructions
discards 8de2d5a52 tcwg_kernel-bisect.sh: Re-arrange code.
discards 96da56ccf tcwg_kernel-bisect.sh: Put bisect test script into artifacts/
discards bdae8b950 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs
discards d772207c8 tcwg_kernel-bisect.sh: Simplify handling of artifact directories
discards 82ffe64ac tcwg_kernel-bisect.sh: Remove --confirm_failure option
discards bedb5b13e round-robin.sh: Improve comment.
adds 964a669f3 round-robin.sh: Improve comment.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (462166953)
\
N -- N -- N refs/changes/50/29850/2 (964a669f3)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 372 --------------------------------------------------
1 file changed, 372 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/50/29850/1
in repository toolchain/jenkins-scripts.
discards 3daf869f8 tcwg_kernel-bisect.sh: Re-arrange code.
discards 14fc33388 tcwg_kernel-bisect.sh: Improve handling of git-bisect edge cases
discards b0d88f505 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop.
discards 91096a80b tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround
discards 4f760ce34 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev.
discards b8866f36d tcwg_kernel-bisect.sh: Update reproduction instructions
discards 10812bcaa tcwg_kernel-bisect.sh: Re-arrange code.
discards 10370ddfa tcwg_kernel-bisect.sh: Put bisect test script into artifacts/
discards 582dd8440 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs
discards 883bead54 tcwg_kernel-bisect.sh: Simplify handling of artifact directories
discards f484163fb tcwg_kernel-bisect.sh: Remove --confirm_failure option
discards c20e3014f round-robin.sh: Improve comment.
adds 1efd682eb round-robin.sh: Improve comment.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (3daf869f8)
\
N -- N -- N refs/changes/50/29850/1 (1efd682eb)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 369 --------------------------------------------------
1 file changed, 369 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/50/29450/2
in repository toolchain/jenkins-scripts.
discards b55571754 tcwg_kernel-bisect.sh: Fix typo.
discards ff8464263 tcwg_kernel-build.sh: Fix typo.
adds 784ddf170 tcwg_kernel-build.sh: Fix typo.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (b55571754)
\
N -- N -- N refs/changes/50/29450/2 (784ddf170)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 248 --------------------------------------------------
1 file changed, 248 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 gcc.
from 129b40529e9 aarch64: Extend aarch64_feature_flags to 128 bits
new c9d61cff97b libstdc++: Remove duplicate include header from ranges_algobase.h
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:
libstdc++-v3/include/bits/ranges_algobase.h | 1 -
1 file changed, 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 reference refs/changes/50/29450/1
in repository toolchain/jenkins-scripts.
discards 87c9f2d6c tcwg_kernel-bisect.sh: Fix typo.
discards 7980e7b79 round-robin.sh, tcwg_kernel-build.sh: Remove ${rr[git_read_only]}
new 8d1c4c36d round-robin.sh, tcwg_kernel-build.sh: Remove ${rr[git_read_only]}
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (87c9f2d6c)
\
N -- N -- N refs/changes/50/29450/1 (8d1c4c36d)
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:
tcwg_kernel-bisect.sh | 248 --------------------------------------------------
1 file changed, 248 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/50/29350/3
in repository toolchain/jenkins-scripts.
discards 85425e8c4 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml
discards e333a4e3d tcwg-update-llvmbot-containers.sh: New job script
adds 4be80ada2 tcwg-update-llvmbot-containers.sh: New job script
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (85425e8c4)
\
N -- N -- N refs/changes/50/29350/3 (4be80ada2)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 230 --------------------------------------------------
1 file changed, 230 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/50/29350/2
in repository toolchain/jenkins-scripts.
discards eca484077 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml
discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects.
discards 148291018 tcwg-update-llvmbot-containers.sh: New job script
adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (eca484077)
\
N -- N -- N refs/changes/50/29350/2 (ce794b80b)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 230 --------------------------------------------------
1 file changed, 230 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/50/29350/1
in repository toolchain/jenkins-scripts.
discards 3cb94b357 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml
discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects.
discards 148291018 tcwg-update-llvmbot-containers.sh: New job script
adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (3cb94b357)
\
N -- N -- N refs/changes/50/29350/1 (ce794b80b)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 230 --------------------------------------------------
1 file changed, 230 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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 reference refs/changes/49/46949/2
in repository toolchain/jenkins-scripts.
discards 5b79d97c2 round-robin-notify.sh: calculate_results_date works even if m [...]
discards 447c2365c round-robin-notify.sh: check_source_changes works even if bas [...]
discards 584cc232b ci-autotest.sh: use get_current_git_dir
adds 01fa109df ci-autotest.sh: use get_current_git_dir
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (5b79d97c2)
\
N -- N -- N refs/changes/49/46949/2 (01fa109df)
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.
No new revisions were added by this update.
Summary of changes:
round-robin-baseline.sh | 624 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2401 -----------------------------------------------
3 files changed, 3711 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
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 reference refs/changes/49/46949/1
in repository toolchain/jenkins-scripts.
discards ab0075481 (WIP) round-robin-notify.sh: calculate_results_date works eve [...]
discards 1fc4e66f6 (WIP) round-robin-notify.sh: check_source_changes works even [...]
discards f5a0e7494 (WIP) ci-autotest.sh: use artifacts/git/${dep}_dir
new 3df3051ae (WIP) ci-autotest.sh: use artifacts/git/${dep}_dir
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (ab0075481)
\
N -- N -- N refs/changes/49/46949/1 (3df3051ae)
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:
round-robin-baseline.sh | 624 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2401 -----------------------------------------------
3 files changed, 3711 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.