This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/85/44685/3
in repository toolchain/jenkins-scripts.
discards dda241b14 jenkins-helpers.sh (run_step): Reduce differences in output
adds 2a6477df0 jenkins-helpers.sh (run_step): Reduce differences in output
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 (dda241b14)
\
N -- N -- N refs/changes/85/44685/3 (2a6477df0)
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/85/44685/2
in repository toolchain/jenkins-scripts.
discards 7a8d8a493 jenkins-helpers.sh (run_step): Reduce differences in output
adds d96a41aa1 jenkins-helpers.sh (run_step): Reduce differences in output
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 (7a8d8a493)
\
N -- N -- N refs/changes/85/44685/2 (d96a41aa1)
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/85/44685/1
in repository toolchain/jenkins-scripts.
discards 93b1c4df8 jenkins-helpers.sh (run_step): Reduce differences in output
adds cd60470ab jenkins-helpers.sh (run_step): Reduce differences in output
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 (93b1c4df8)
\
N -- N -- N refs/changes/85/44685/1 (cd60470ab)
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/85/44585/2
in repository toolchain/jenkins-scripts.
discards fb620282a tcwg-benchmark-results.sh: Pass --threshold_interesting=10 to [...]
adds 80994154c tcwg-benchmark-results.sh: Pass --threshold_interesting=10 to [...]
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 (fb620282a)
\
N -- N -- N refs/changes/85/44585/2 (80994154c)
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/85/44585/1
in repository toolchain/jenkins-scripts.
discards 65f9154be tcwg-benchmark-results.sh: Pass --threshold_interesting=10 to [...]
new b597da33f tcwg-benchmark-results.sh: Pass --threshold_interesting=10 to [...]
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 (65f9154be)
\
N -- N -- N refs/changes/85/44585/1 (b597da33f)
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/85/44385/9
in repository toolchain/jenkins-scripts.
discards 21d97ff07 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds c6ce4170f docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (21d97ff07)
\
N -- N -- N refs/changes/85/44385/9 (c6ce4170f)
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/85/44385/8
in repository toolchain/jenkins-scripts.
discards b3af81917 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds b4767c96f docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (b3af81917)
\
N -- N -- N refs/changes/85/44385/8 (b4767c96f)
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/85/44385/7
in repository toolchain/jenkins-scripts.
discards 765ff9596 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds c86d8ae3f docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (765ff9596)
\
N -- N -- N refs/changes/85/44385/7 (c86d8ae3f)
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/85/44385/6
in repository toolchain/jenkins-scripts.
discards 3d28e1415 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds ebe570a91 docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (3d28e1415)
\
N -- N -- N refs/changes/85/44385/6 (ebe570a91)
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/85/44385/5
in repository toolchain/jenkins-scripts.
discards e4da97c1a docker-run.sh: Add new options: ++rsync_to and ++rsync_from
adds 7457d72ce docker-run.sh: Add new options: ++rsync_to and ++rsync_from
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 (e4da97c1a)
\
N -- N -- N refs/changes/85/44385/5 (7457d72ce)
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.