This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/06/39306/1
in repository toolchain/jenkins-scripts.
discards 5ddec02ed tcwg-benchmark.sh: Improve verbosity handling
adds 269df0178 tcwg-benchmark.sh: Improve verbosity handling
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 (5ddec02ed)
\
N -- N -- N refs/changes/06/39306/1 (269df0178)
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:
--
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/06/39006/1
in repository toolchain/jenkins-scripts.
discards b05ff725f round-robin-bisect.sh: Notify patch authors on regressions
discards ebe8198d9 tcwg-benchmark.sh: Return infrastructure error on problems with HW
adds 53c210055 tcwg-benchmark.sh: Return infrastructure error on problems with HW
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 (b05ff725f)
\
N -- N -- N refs/changes/06/39006/1 (53c210055)
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-bisect.sh | 748 --------------------------------------------------
1 file changed, 748 deletions(-)
delete mode 100755 round-robin-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/06/38006/2
in repository toolchain/jenkins-scripts.
discards 548cf38e5 tcwg-update-llvmbot-containers.sh: Run two more libcxx bots o [...]
adds fffdceb7c tcwg-update-llvmbot-containers.sh: Run two more libcxx bots o [...]
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 (548cf38e5)
\
N -- N -- N refs/changes/06/38006/2 (fffdceb7c)
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:
--
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/06/38006/1
in repository toolchain/jenkins-scripts.
discards 4099663dc tcwg-update-llvmbot-containers.sh: Run two more libcxx bots o [...]
new 8740c2328 tcwg-update-llvmbot-containers.sh: Run two more libcxx bots o [...]
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 (4099663dc)
\
N -- N -- N refs/changes/06/38006/1 (8740c2328)
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 reference refs/changes/06/37406/2
in repository toolchain/jenkins-scripts.
discards 8b78dcbbb round-robin-bisect.sh: Generalize logic of handling "reset" commit
discards 499beadee round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (8b78dcbbb)
\
N -- N -- N refs/changes/06/37406/2 (e1b7cb695)
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-bisect.sh | 720 --------------------------------------------------
1 file changed, 720 deletions(-)
delete mode 100755 round-robin-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/06/37406/1
in repository toolchain/jenkins-scripts.
discards 9f50f518c round-robin-bisect.sh: Generalize logic of handling "reset" commit
discards fbdf19b02 round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (9f50f518c)
\
N -- N -- N refs/changes/06/37406/1 (e1b7cb695)
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-bisect.sh | 720 --------------------------------------------------
1 file changed, 720 deletions(-)
delete mode 100755 round-robin-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/06/37306/1
in repository toolchain/jenkins-scripts.
discards 4654e5907 round-robin.sh: Update build_llvm to use new monorepo layout
adds 9f80c86f1 round-robin.sh: Update build_llvm to use new monorepo layout
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 (4654e5907)
\
N -- N -- N refs/changes/06/37306/1 (9f80c86f1)
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:
--
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/06/37206/1
in repository toolchain/jenkins-scripts.
discards 3ecb43c59 round-robin.sh: Allow non-broken components to advance their [...]
adds efe6b5361 round-robin.sh: Allow non-broken components to advance their [...]
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 (3ecb43c59)
\
N -- N -- N refs/changes/06/37206/1 (efe6b5361)
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:
--
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/06/34906/2
in repository toolchain/jenkins-scripts.
discards b39cebb22 jenkins-helpers.sh: Rework print_host_for_node to rely only on ssh
adds 6d95b9010 jenkins-helpers.sh: Rework print_host_for_node to rely only on ssh
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 (b39cebb22)
\
N -- N -- N refs/changes/06/34906/2 (6d95b9010)
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:
--
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/06/34906/1
in repository toolchain/jenkins-scripts.
discards 09e6b6c27 jenkins-helpers.sh: Rework print_host_for_node to rely only on ssh
new e35caac89 jenkins-helpers.sh: Rework print_host_for_node to rely only on ssh
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 (09e6b6c27)
\
N -- N -- N refs/changes/06/34906/1 (e35caac89)
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.