This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/72/45572/1
in repository toolchain/jenkins-scripts.
discards bf7ba7d6f round-robin-notify.sh (post_interesting_commits): Use gitolite
new b03ddd49a round-robin-notify.sh (post_interesting_commits): Use gitolite
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 (bf7ba7d6f)
\
N -- N -- N refs/changes/72/45572/1 (b03ddd49a)
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/72/45472/3
in repository toolchain/jenkins-scripts.
discards ac27d7b76 tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
adds 380f48280 tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
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 (ac27d7b76)
\
N -- N -- N refs/changes/72/45472/3 (380f48280)
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/72/45472/2
in repository toolchain/jenkins-scripts.
discards b411ed5ab tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
adds 786df1bd0 tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
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 (b411ed5ab)
\
N -- N -- N refs/changes/72/45472/2 (786df1bd0)
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/72/45472/1
in repository toolchain/jenkins-scripts.
discards b4bbd29cd tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
adds 74990f888 tcwg_bmk-build.sh: Merge no_regression_p/compare_results routines
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 (b4bbd29cd)
\
N -- N -- N refs/changes/72/45472/1 (74990f888)
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/72/45272/1
in repository toolchain/jenkins-scripts.
discards deb36ca9e round-robin-bisect.sh: Convert bad_branch into bad_branch_rev
discards e3886e687 round-robin-notify.sh (print_mail_body): Use print_jira_card_key
discards 7d616c035 round-robin-notify.sh (print_mail_body): Make the regression [...]
discards 934531cfc round-robin.sh: Start bisection from top of branch, rather th [...]
adds 7efdc03f4 round-robin.sh: Start bisection from top of branch, rather th [...]
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 (deb36ca9e)
\
N -- N -- N refs/changes/72/45272/1 (7efdc03f4)
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 | 410 -------------
round-robin-bisect.sh | 658 --------------------
round-robin-notify.sh | 1535 -----------------------------------------------
3 files changed, 2603 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/72/44972/3
in repository toolchain/jenkins-scripts.
discards 6f3d4114d tcwg-update-llvmbot-containers: Move aarch64-libcxx-01 back t [...]
adds 6146361ad tcwg-update-llvmbot-containers: Move aarch64-libcxx-01 back t [...]
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 (6f3d4114d)
\
N -- N -- N refs/changes/72/44972/3 (6146361ad)
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/72/44972/2
in repository toolchain/jenkins-scripts.
discards cc47d7fc3 tcwg-update-llvmbot-containers: Move aarch64-libcxx-01 back t [...]
new 46d150b79 tcwg-update-llvmbot-containers: Move aarch64-libcxx-01 back t [...]
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 (cc47d7fc3)
\
N -- N -- N refs/changes/72/44972/2 (46d150b79)
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/72/44972/1
in repository toolchain/jenkins-scripts.
discards d473d5e07 tcwg-update-llvmbot-containers: Move libcxx-01 back to jade-04
new 1cdc39092 tcwg-update-llvmbot-containers: Move libcxx-01 back to jade-04
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 (d473d5e07)
\
N -- N -- N refs/changes/72/44972/1 (1cdc39092)
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/72/44372/4
in repository toolchain/jenkins-scripts.
discards 771c8b6d5 jenkins-helpers.sh (print_host_for_node): Use preferred redir [...]
adds 39922d1a9 jenkins-helpers.sh (print_host_for_node): Use preferred redir [...]
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 (771c8b6d5)
\
N -- N -- N refs/changes/72/44372/4 (39922d1a9)
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/72/44372/3
in repository toolchain/jenkins-scripts.
discards 16ff7fc68 jenkins-helpers.sh (print_host_for_node): Use preferred redir [...]
adds 5a5ff4295 jenkins-helpers.sh (print_host_for_node): Use preferred redir [...]
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 (16ff7fc68)
\
N -- N -- N refs/changes/72/44372/3 (5a5ff4295)
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.