This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/93/45593/2
in repository toolchain/jenkins-scripts.
discards a210fed36 round-robin-notify.sh (print_email_recipients): Fix "to:" emails
discards 487a182d0 round-robin-baseline.sh (push_baseline): Delete branches in t [...]
discards 667d2a7cc tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data
adds eeb8e5335 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data
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 (a210fed36)
\
N -- N -- N refs/changes/93/45593/2 (eeb8e5335)
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 | 464 --------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1610 -----------------------------------------------
3 files changed, 2729 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/93/45593/1
in repository toolchain/jenkins-scripts.
discards 0c4760cb8 round-robin-notify.sh (print_email_recipients): Fix "to:" emails
discards 2bcc35809 tcwg_bmk-build.sh (benchmark): Improve wait cycle
new 290a46743 tcwg_bmk-build.sh (benchmark): Improve wait cycle
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 (0c4760cb8)
\
N -- N -- N refs/changes/93/45593/1 (290a46743)
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:
round-robin-baseline.sh | 464 --------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1610 -----------------------------------------------
3 files changed, 2729 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/93/45293/2
in repository toolchain/jenkins-scripts.
discards 78cf7c7fc start-container-docker.sh: Cleanup containers using container IDs
adds dbd333b11 start-container-docker.sh: Cleanup containers using container IDs
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 (78cf7c7fc)
\
N -- N -- N refs/changes/93/45293/2 (dbd333b11)
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/93/45293/1
in repository toolchain/jenkins-scripts.
discards 912511f09 start-container-docker.sh: Cleanup containers using container IDs
adds ad1551b78 start-container-docker.sh: Cleanup containers using container IDs
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 (912511f09)
\
N -- N -- N refs/changes/93/45293/1 (ad1551b78)
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/93/44693/5
in repository toolchain/jenkins-scripts.
discards 1949cf299 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
adds 2bc17245b tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
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 (1949cf299)
\
N -- N -- N refs/changes/93/44693/5 (2bc17245b)
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/93/44693/4
in repository toolchain/jenkins-scripts.
discards db15770d2 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
new eb92a3015 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
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 (db15770d2)
\
N -- N -- N refs/changes/93/44693/4 (eb92a3015)
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/93/44693/3
in repository toolchain/jenkins-scripts.
discards 2218baca6 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
new e6db00aee tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
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 (2218baca6)
\
N -- N -- N refs/changes/93/44693/3 (e6db00aee)
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/93/44693/2
in repository toolchain/jenkins-scripts.
discards 59e129a01 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
new 14c933bce tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
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 (59e129a01)
\
N -- N -- N refs/changes/93/44693/2 (14c933bce)
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/93/44693/1
in repository toolchain/jenkins-scripts.
discards b4076f8e4 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
new 372b55a54 tcwg_gnu-build.sh (no_regression_p): Move non-essential analysis
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 (b4076f8e4)
\
N -- N -- N refs/changes/93/44693/1 (372b55a54)
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/93/44493/4
in repository toolchain/jenkins-scripts.
discards 93ccf44a7 round-robin-baseline.sh: Trim artifacts history only if pushing it.
discards e3ca4ff57 round-robin-baseline.sh: New script to host update_baseline() code
adds 59aa31e54 round-robin-baseline.sh: New script to host update_baseline() code
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 (93ccf44a7)
\
N -- N -- N refs/changes/93/44493/4 (59aa31e54)
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 | 169 -------
round-robin-bisect.sh | 653 ------------------------
round-robin-notify.sh | 1255 -----------------------------------------------
3 files changed, 2077 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.