This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/56/45256/3
in repository toolchain/jenkins-scripts.
discards 36a2dfd37 round-robin-notify.sh: Add new "--notify precommit" mode
discards f6229827c docker-run.sh: Remove ++rsync_to/++rsync_from unused options
adds 7a42dd907 docker-run.sh: Remove ++rsync_to/++rsync_from unused options
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 (36a2dfd37)
\
N -- N -- N refs/changes/56/45256/3 (7a42dd907)
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 | 410 -------------
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1521 -----------------------------------------------
3 files changed, 2584 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/56/45256/2
in repository toolchain/jenkins-scripts.
discards 273c8ff0d round-robin-notify.sh: Add new "--notify precommit" mode
discards e296e5d71 docker-run.sh: Remove ++rsync_to/++rsync_from unused options
new 8107d961b docker-run.sh: Remove ++rsync_to/++rsync_from unused options
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 (273c8ff0d)
\
N -- N -- N refs/changes/56/45256/2 (8107d961b)
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 | 410 -------------
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1521 -----------------------------------------------
3 files changed, 2584 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/56/45256/1
in repository toolchain/jenkins-scripts.
discards 854c9e7fe round-robin-notify.sh: Add new "--notify precommit" mode
discards e296e5d71 docker-run.sh: Remove ++rsync_to/++rsync_from unused options
new 8107d961b docker-run.sh: Remove ++rsync_to/++rsync_from unused options
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 (854c9e7fe)
\
N -- N -- N refs/changes/56/45256/1 (8107d961b)
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 | 410 -------------
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1519 -----------------------------------------------
3 files changed, 2582 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/56/45056/1
in repository toolchain/jenkins-scripts.
discards eaeaa3d25 pw-report.sh: Cleanup
adds fc9bd6792 pw-report.sh: Cleanup
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 (eaeaa3d25)
\
N -- N -- N refs/changes/56/45056/1 (fc9bd6792)
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/56/44656/2
in repository toolchain/jenkins-scripts.
discards 966d4bc67 Revert "tcwg-benchmark.sh: Add results_dest parameter to spec [...]
adds 315da1797 Revert "tcwg-benchmark.sh: Add results_dest parameter to spec [...]
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 (966d4bc67)
\
N -- N -- N refs/changes/56/44656/2 (315da1797)
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/56/44656/1
in repository toolchain/jenkins-scripts.
discards 40842facd Revert "tcwg-benchmark.sh: Add results_dest parameter to spec [...]
new 695fd35fb Revert "tcwg-benchmark.sh: Add results_dest parameter to spec [...]
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 (40842facd)
\
N -- N -- N refs/changes/56/44656/1 (695fd35fb)
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/56/44456/2
in repository toolchain/jenkins-scripts.
discards e325b703e round-robin-notify.sh: Fix previous commit on cp rewrite
discards bd83c423a tcwg_gnu-build.sh,cimonitor: Adapt scripts for new ci_project [...]
adds 18ae3bf6b tcwg_gnu-build.sh,cimonitor: Adapt scripts for new ci_project [...]
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 (e325b703e)
\
N -- N -- N refs/changes/56/44456/2 (18ae3bf6b)
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-bisect.sh | 647 -------------------------
round-robin-notify.sh | 1246 -------------------------------------------------
2 files changed, 1893 deletions(-)
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/56/44456/1
in repository toolchain/jenkins-scripts.
discards 9067e42dc round-robin-notify.sh: Fix previous commit on cp rewrite
discards c1f85ef2b round-robin-notify.sh: small cp rewrite
discards 6b9aa7f24 start-container-docker.sh: Add "--task precommit"
adds 079343338 start-container-docker.sh: Add "--task precommit"
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 (9067e42dc)
\
N -- N -- N refs/changes/56/44456/1 (079343338)
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-bisect.sh | 647 --------------------------
round-robin-notify.sh | 1237 -------------------------------------------------
2 files changed, 1884 deletions(-)
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/56/44356/2
in repository toolchain/jenkins-scripts.
discards a89b765d4 jenkins-helpers.sh (assert_with_msg): Print error message to stderr
adds 21458aed5 jenkins-helpers.sh (assert_with_msg): Print error message to stderr
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 (a89b765d4)
\
N -- N -- N refs/changes/56/44356/2 (21458aed5)
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/56/44356/1
in repository toolchain/jenkins-scripts.
discards 9ea700022 jenkins-helpers.sh (assert_with_msg): Print error message to stderr
adds 27a73aa44 jenkins-helpers.sh (assert_with_msg): Print error message to stderr
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 (9ea700022)
\
N -- N -- N refs/changes/56/44356/1 (27a73aa44)
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.