This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/59/45159/1
in repository toolchain/jenkins-scripts.
discards d57715a35 tcwg_gnu-build.sh: Increase manifest major version
adds e5c65993c tcwg_gnu-build.sh: Increase manifest major version
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 (d57715a35)
\
N -- N -- N refs/changes/59/45159/1 (e5c65993c)
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/59/44159/1
in repository toolchain/jenkins-scripts.
discards b97792fa6 round-robin.sh (update_baseline): Move base-artifacts/ rewrite code
adds e03d1ef55 round-robin.sh (update_baseline): Move base-artifacts/ rewrite 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 (b97792fa6)
\
N -- N -- N refs/changes/59/44159/1 (e03d1ef55)
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/59/42559/2
in repository toolchain/jenkins-scripts.
discards cca981228 tcwg_bmk-build.sh: compare_results handles if there's no metr [...]
adds 8f9110c44 tcwg_bmk-build.sh: compare_results handles if there's no metr [...]
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 (cca981228)
\
N -- N -- N refs/changes/59/42559/2 (8f9110c44)
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/59/42559/1
in repository toolchain/jenkins-scripts.
discards 23ab852a8 tcwg_bmk-build.sh: compare_results handles if there's no metr [...]
new 89e6d9c07 tcwg_bmk-build.sh: compare_results handles if there's no metr [...]
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 (23ab852a8)
\
N -- N -- N refs/changes/59/42559/1 (89e6d9c07)
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/59/41959/5
in repository toolchain/jenkins-scripts.
discards 0a46a6c95 tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
adds 45737e96a tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
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 (0a46a6c95)
\
N -- N -- N refs/changes/59/41959/5 (45737e96a)
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/59/41959/4
in repository toolchain/jenkins-scripts.
discards c95e046bc tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
adds 1d12a6eaa tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
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 (c95e046bc)
\
N -- N -- N refs/changes/59/41959/4 (1d12a6eaa)
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/59/41959/3
in repository toolchain/jenkins-scripts.
discards 24dfdb932 tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
adds 3a16334de tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
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 (24dfdb932)
\
N -- N -- N refs/changes/59/41959/3 (3a16334de)
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/59/41959/2
in repository toolchain/jenkins-scripts.
discards ffe47f27f tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
adds 40ef9bf95 tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
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 (ffe47f27f)
\
N -- N -- N refs/changes/59/41959/2 (40ef9bf95)
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/59/41959/1
in repository toolchain/jenkins-scripts.
discards e79344e92 tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
adds 7617e02e0 tcwg_bmk-build.sh: Remove obsolete support for *-vs-* builds
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 (e79344e92)
\
N -- N -- N refs/changes/59/41959/1 (7617e02e0)
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/59/41859/1
in repository toolchain/jenkins-scripts.
discards 7597b10e8 round-robin.sh: Update comments
adds 8b2f582eb round-robin.sh: Update comments
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 (7597b10e8)
\
N -- N -- N refs/changes/59/41859/1 (8b2f582eb)
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.