This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/34/45534/4
in repository toolchain/jenkins-scripts.
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 (2bcc35809)
\
N -- N -- N refs/changes/34/45534/4 (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:
--
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/34/45534/3
in repository toolchain/jenkins-scripts.
discards ac1ed5f46 tcwg_bmk-build.sh (benchmark): Improve wait cycle
adds 8d16f3844 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 (ac1ed5f46)
\
N -- N -- N refs/changes/34/45534/3 (8d16f3844)
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/34/45534/2
in repository toolchain/jenkins-scripts.
discards b28eb4939 tcwg_bmk-build.sh (benchmark): Improve wait cycle
adds 8cd8db3cd 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 (b28eb4939)
\
N -- N -- N refs/changes/34/45534/2 (8cd8db3cd)
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/34/45534/13
in repository toolchain/jenkins-scripts.
discards 047232cc7 tcwg_bmk-build.sh (benchmark): Improve wait cycle
adds 347340a2c 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 (047232cc7)
\
N -- N -- N refs/changes/34/45534/13 (347340a2c)
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/34/45534/12
in repository toolchain/jenkins-scripts.
discards 8ad1fe486 tcwg_bmk-build.sh (benchmark): Improve wait cycle
new 4a952f710 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 (8ad1fe486)
\
N -- N -- N refs/changes/34/45534/12 (4a952f710)
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/34/45534/11
in repository toolchain/jenkins-scripts.
discards c8377a810 tcwg_bmk-build.sh (benchmark): Improve wait cycle
adds 7d34d83fd 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 (c8377a810)
\
N -- N -- N refs/changes/34/45534/11 (7d34d83fd)
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/34/45534/10
in repository toolchain/jenkins-scripts.
discards f10e8743e tcwg_bmk-build.sh (benchmark): Improve wait cycle
adds 60b39d98f 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 (f10e8743e)
\
N -- N -- N refs/changes/34/45534/10 (60b39d98f)
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/34/45534/1
in repository toolchain/jenkins-scripts.
discards f2af59e44 tcwg_bmk-build.sh (benchmark): Improve wait cycle
new f1c0d68f0 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 (f2af59e44)
\
N -- N -- N refs/changes/34/45534/1 (f1c0d68f0)
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/34/45334/1
in repository toolchain/jenkins-scripts.
discards 3e655e996 start-container-docker.sh: Debug cleanup of secondary containers
adds 5be0afca0 start-container-docker.sh: Debug cleanup of secondary containers
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 (3e655e996)
\
N -- N -- N refs/changes/34/45334/1 (5be0afca0)
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/34/44634/5
in repository toolchain/jenkins-scripts.
discards d82af6b4d round-robin*.sh: Use ${rr[no_regression_result]}
adds eccdb5045 round-robin*.sh: Use ${rr[no_regression_result]}
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 (d82af6b4d)
\
N -- N -- N refs/changes/34/44634/5 (eccdb5045)
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.