This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/25/47325/1
in repository toolchain/jenkins-scripts.
discards 419c5aa0f round-robin-notify.sh: Replace "progression" with "improvement"
discards b2ef441e3 round-robin-notify.sh: fetching tags if needed
discards 251f4858b tcwg-benchmark-results.sh: status_csv passed to interesting s [...]
adds 4a8c24605 tcwg-benchmark-results.sh: status_csv passed to interesting s [...]
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 (419c5aa0f)
\
N -- N -- N refs/changes/25/47325/1 (4a8c24605)
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 | 650 -------------
round-robin-bisect.sh | 735 --------------
round-robin-notify.sh | 2429 -----------------------------------------------
3 files changed, 3814 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/25/47125/1
in repository toolchain/jenkins-scripts.
discards b45d8387a tcwg-report-stale-rr-jobs.sh: Adapt to use remote get_git_history
adds ed96fe817 tcwg-report-stale-rr-jobs.sh: Adapt to use remote get_git_history
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 (b45d8387a)
\
N -- N -- N refs/changes/25/47125/1 (ed96fe817)
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/25/46925/1
in repository toolchain/jenkins-scripts.
discards 49d3a8b60 update_components_revs.sh: Fix dynamic_components_list
adds a36897aca update_components_revs.sh: Fix dynamic_components_list
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 (49d3a8b60)
\
N -- N -- N refs/changes/25/46925/1 (a36897aca)
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/25/46725/6
in repository toolchain/jenkins-scripts.
discards b4e2c4744 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
adds a60f68d1f tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (b4e2c4744)
\
N -- N -- N refs/changes/25/46725/6 (a60f68d1f)
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/25/46725/5
in repository toolchain/jenkins-scripts.
discards 9bfd0ec45 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
new eca52e1ae tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (9bfd0ec45)
\
N -- N -- N refs/changes/25/46725/5 (eca52e1ae)
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/25/46725/4
in repository toolchain/jenkins-scripts.
discards 21ee182bc tcwg_bmk-build.sh: upgrade minor version for some bmk projects
new bf31ed5fa tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (21ee182bc)
\
N -- N -- N refs/changes/25/46725/4 (bf31ed5fa)
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/25/46725/3
in repository toolchain/jenkins-scripts.
discards 6ff921c47 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
new b24d0fc57 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (6ff921c47)
\
N -- N -- N refs/changes/25/46725/3 (b24d0fc57)
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/25/46725/2
in repository toolchain/jenkins-scripts.
discards 1f5f43d96 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
new 0c173a0e4 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (1f5f43d96)
\
N -- N -- N refs/changes/25/46725/2 (0c173a0e4)
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/25/46725/1
in repository toolchain/jenkins-scripts.
discards e891c5ba0 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
new 5d8bfe251 tcwg_bmk-build.sh: upgrade minor version for some bmk projects
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 (e891c5ba0)
\
N -- N -- N refs/changes/25/46725/1 (5d8bfe251)
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/25/46225/1
in repository toolchain/jenkins-scripts.
discards 3286c0602 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Handle [...]
adds 52a53f178 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Handle [...]
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 (3286c0602)
\
N -- N -- N refs/changes/25/46225/1 (52a53f178)
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.