This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/39/46439/4
in repository toolchain/jenkins-scripts.
discards 676ae4948 tcwg_bmk-config.sh,round-robin.sh: Add cpu information
new 7db324793 tcwg_bmk-config.sh,round-robin.sh: Add cpu information
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 (676ae4948)
\
N -- N -- N refs/changes/39/46439/4 (7db324793)
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/39/46439/3
in repository toolchain/jenkins-scripts.
discards 7a7af1b71 tcwg_bmk-config.sh,round-robin.sh: Add cpu information
new 4b614fc68 tcwg_bmk-config.sh,round-robin.sh: Add cpu information
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 (7a7af1b71)
\
N -- N -- N refs/changes/39/46439/3 (4b614fc68)
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/39/46439/2
in repository toolchain/jenkins-scripts.
discards 13a2a433b tcwg_bmk-config.sh,round-robin.sh: Add cpu information
new 5af5a1825 tcwg_bmk-config.sh,round-robin.sh: Add cpu information
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 (13a2a433b)
\
N -- N -- N refs/changes/39/46439/2 (5af5a1825)
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/39/46439/1
in repository toolchain/jenkins-scripts.
discards 9c08f0e88 tcwg_bmk-config.sh: Add cpu information to be used in benchmarking
new 48869c9ad tcwg_bmk-config.sh: Add cpu information to be used in benchmarking
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 (9c08f0e88)
\
N -- N -- N refs/changes/39/46439/1 (48869c9ad)
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/39/46139/2
in repository toolchain/jenkins-scripts.
discards b3101c209 tcwg_gnu-build.sh: Remove local glibc patch
adds 4dd5b8681 tcwg_gnu-build.sh: Remove local glibc patch
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 (b3101c209)
\
N -- N -- N refs/changes/39/46139/2 (4dd5b8681)
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/39/46139/1
in repository toolchain/jenkins-scripts.
discards 4e48736ae tcwg_gnu-build.sh: Remove local glibc patch
new b6fb3d265 tcwg_gnu-build.sh: Remove local glibc patch
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 (4e48736ae)
\
N -- N -- N refs/changes/39/46139/1 (b6fb3d265)
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/39/45639/3
in repository toolchain/jenkins-scripts.
discards 0c21bd770 tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
adds 6d0ca2ff9 tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
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 (0c21bd770)
\
N -- N -- N refs/changes/39/45639/3 (6d0ca2ff9)
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/39/45639/2
in repository toolchain/jenkins-scripts.
discards 87f2219ab tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
new 5ecee8166 tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
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 (87f2219ab)
\
N -- N -- N refs/changes/39/45639/2 (5ecee8166)
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/39/45639/1
in repository toolchain/jenkins-scripts.
discards 1755d0c52 tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
new 1eb82fe72 tcwg_bmk-build.sh: Fix init mode, failing due to a wrong assertion
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 (1755d0c52)
\
N -- N -- N refs/changes/39/45639/1 (1eb82fe72)
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/39/45239/6
in repository toolchain/jenkins-scripts.
discards 2bbd76eaf round-robin-notify.sh (print_mail_body): Use print_jira_card_key
discards 146e3b504 round-robin-notify.sh (gnu_print_result): Do not print out em [...]
discards ea0efb4f1 round-robin.sh (create_trigger_files): Fix typo
adds 3de51ca69 round-robin.sh (create_trigger_files): Fix typo
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 (2bbd76eaf)
\
N -- N -- N refs/changes/39/45239/6 (3de51ca69)
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 | 1543 -----------------------------------------------
3 files changed, 2606 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.