This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/02/45702/3
in repository toolchain/jenkins-scripts.
discards 17d36081f round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards 03877dae5 jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
adds e498d7bff jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
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 (17d36081f)
\
N -- N -- N refs/changes/02/45702/3 (e498d7bff)
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 | 524 --------------
round-robin-bisect.sh | 678 ------------------
round-robin-notify.sh | 1738 -----------------------------------------------
3 files changed, 2940 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/02/45702/2
in repository toolchain/jenkins-scripts.
discards e29a02204 round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards c21c34105 round-robin-baseline.sh (rewrite_single_revision): Add assert
discards 197d50292 tcwg_gnu-build.sh: Bump minor version to update jira cards
adds ead51574c tcwg_gnu-build.sh: Bump minor version to update jira cards
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 (e29a02204)
\
N -- N -- N refs/changes/02/45702/2 (ead51574c)
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 | 524 --------------
round-robin-bisect.sh | 655 ------------------
round-robin-notify.sh | 1738 -----------------------------------------------
3 files changed, 2917 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/02/45702/1
in repository toolchain/jenkins-scripts.
discards c5eff2fce round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards 197d50292 tcwg_gnu-build.sh: Bump minor version to update jira cards
adds ead51574c tcwg_gnu-build.sh: Bump minor version to update jira cards
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 (c5eff2fce)
\
N -- N -- N refs/changes/02/45702/1 (ead51574c)
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 | 516 --------------
round-robin-bisect.sh | 655 ------------------
round-robin-notify.sh | 1738 -----------------------------------------------
3 files changed, 2909 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/02/44602/2
in repository toolchain/jenkins-scripts.
discards 3dd8daf2d pw-report.sh: Submit failure-to-apply as a warning check
adds e86ed1d94 pw-report.sh: Submit failure-to-apply as a warning check
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 (3dd8daf2d)
\
N -- N -- N refs/changes/02/44602/2 (e86ed1d94)
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/02/44602/1
in repository toolchain/jenkins-scripts.
discards c169acdb0 pw-report.sh: Submit failure-to-apply as a warning check
new 13bef4f98 pw-report.sh: Submit failure-to-apply as a warning check
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 (c169acdb0)
\
N -- N -- N refs/changes/02/44602/1 (13bef4f98)
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/02/44302/2
in repository toolchain/jenkins-scripts.
discards 5bed60828 generate-cimonitor-dashboard.py: Add bmk_results in for-ci-de [...]
adds a84f6315c generate-cimonitor-dashboard.py: Add bmk_results in for-ci-de [...]
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 (5bed60828)
\
N -- N -- N refs/changes/02/44302/2 (a84f6315c)
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/02/44302/1
in repository toolchain/jenkins-scripts.
discards 370dcdc95 generate-cimonitor-dashboard.py: Add bmk_results in for-ci-de [...]
new a480d03a9 generate-cimonitor-dashboard.py: Add bmk_results in for-ci-de [...]
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 (370dcdc95)
\
N -- N -- N refs/changes/02/44302/1 (a480d03a9)
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/02/42802/1
in repository toolchain/jenkins-scripts.
discards 8f1fef301 tcwg-report-stale-rr-jobs.sh: find project corresponding to t [...]
adds e7cba84ad tcwg-report-stale-rr-jobs.sh: find project corresponding to 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 (8f1fef301)
\
N -- N -- N refs/changes/02/42802/1 (e7cba84ad)
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/02/41602/2
in repository toolchain/jenkins-scripts.
discards ea3cd249d tcwg_bmk-build.sh: check existance of ssh_host/ssh_port when [...]
adds c16515f80 tcwg_bmk-build.sh: check existance of ssh_host/ssh_port when [...]
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 (ea3cd249d)
\
N -- N -- N refs/changes/02/41602/2 (c16515f80)
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/02/41602/1
in repository toolchain/jenkins-scripts.
discards 8c697095d tcwg_bmk-build.sh: check existance of ssh_host/ssh_port when [...]
new f5b166550 tcwg_bmk-build.sh: check existance of ssh_host/ssh_port when [...]
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 (8c697095d)
\
N -- N -- N refs/changes/02/41602/1 (f5b166550)
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.