This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/83/45883/2
in repository toolchain/jenkins-scripts.
discards 0163d4032 lnt-utils.sh: Fix expression for finding sum files
adds c2a37f234 lnt-utils.sh: Fix expression for finding sum files
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 (0163d4032)
\
N -- N -- N refs/changes/83/45883/2 (c2a37f234)
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/83/45883/1
in repository toolchain/jenkins-scripts.
discards 31b54f082 lnt-utils.sh: Fix expression for finding sum files
new a6b434f35 lnt-utils.sh: Fix expression for finding sum files
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 (31b54f082)
\
N -- N -- N refs/changes/83/45883/1 (a6b434f35)
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/83/44783/2
in repository toolchain/jenkins-scripts.
discards 48880107d round-robin-notify.sh (post_interesting_commits): Better clea [...]
adds f82e2451e round-robin-notify.sh (post_interesting_commits): Better clea [...]
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 (48880107d)
\
N -- N -- N refs/changes/83/44783/2 (f82e2451e)
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/83/44783/1
in repository toolchain/jenkins-scripts.
discards 7a1f787f7 round-robin-notify.sh (post_interesting_commits): Better clea [...]
new b14475c16 round-robin-notify.sh (post_interesting_commits): Better clea [...]
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 (7a1f787f7)
\
N -- N -- N refs/changes/83/44783/1 (b14475c16)
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/83/44583/3
in repository toolchain/jenkins-scripts.
discards 3f4f1d952 round-robin-notify.sh: Replace regenerate_regression_details()
discards 7d29d66ca round-robin-notify.sh: Add a comment
discards 5f6b078f6 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation
adds 810278793 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation
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 (3f4f1d952)
\
N -- N -- N refs/changes/83/44583/3 (810278793)
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 | 166 ------
round-robin-bisect.sh | 653 -----------------------
round-robin-notify.sh | 1333 -----------------------------------------------
3 files changed, 2152 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/83/44583/2
in repository toolchain/jenkins-scripts.
discards fc568bf52 round-robin-notify.sh: Replace regenerate_regression_details()
discards e607eb3e1 round-robin-notify.sh: Add a comment
discards 8afcd0137 round-robin-notify.sh: Fixed commit display
discards 9e6758923 round-robin-notify.sh: Replace reproduction instruction by a link
discards 0c4cf34ea round-robin-notify.sh: Replace full commit by its link
discards 67e377147 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust
adds 94e78ef96 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust
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 (fc568bf52)
\
N -- N -- N refs/changes/83/44583/2 (94e78ef96)
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 | 166 ------
round-robin-bisect.sh | 653 -----------------------
round-robin-notify.sh | 1333 -----------------------------------------------
3 files changed, 2152 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/83/44583/1
in repository toolchain/jenkins-scripts.
discards 5db91ba7c round-robin-notify.sh: Replace regenerate_regression_details()
discards 9a7d4a0f6 round-robin-notify.sh: Add a comment
discards 67e377147 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust
adds 94e78ef96 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust
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 (5db91ba7c)
\
N -- N -- N refs/changes/83/44583/1 (94e78ef96)
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 | 166 ------
round-robin-bisect.sh | 653 ------------------------
round-robin-notify.sh | 1290 -----------------------------------------------
3 files changed, 2109 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/83/44383/9
in repository toolchain/jenkins-scripts.
discards 001d3c2d8 jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
adds 8574308c7 jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
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 (001d3c2d8)
\
N -- N -- N refs/changes/83/44383/9 (8574308c7)
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/83/44383/8
in repository toolchain/jenkins-scripts.
discards 8a1d19b5e jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
adds 74668e7a0 jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
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 (8a1d19b5e)
\
N -- N -- N refs/changes/83/44383/8 (74668e7a0)
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/83/44383/7
in repository toolchain/jenkins-scripts.
discards fa11b6425 jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
adds ad783d742 jenkins-helpers.sh (wait_for_ssh_server): Allow more ssh options
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 (fa11b6425)
\
N -- N -- N refs/changes/83/44383/7 (ad783d742)
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.