This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/13/46213/7
in repository toolchain/jenkins-scripts.
discards b630a6b5e round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 7149668cd round-robin-notify.sh: Generate a publish html file for jenkins job
discards 6be09e13f round-robin-notify.sh: Typo
discards 94384c3cc lnt-utils.sh: Add git revision infos for the build
adds e7515666e lnt-utils.sh: Add git revision infos for the build
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 (b630a6b5e)
\
N -- N -- N refs/changes/13/46213/7 (e7515666e)
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 | 567 -------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 2076 -----------------------------------------------
3 files changed, 3324 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/13/46213/6
in repository toolchain/jenkins-scripts.
discards 75272c8f8 round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 7298d0ccb round-robin.sh: Move testresults2jenkins.sh to ABE
adds c8545fb05 round-robin.sh: Move testresults2jenkins.sh to ABE
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 (75272c8f8)
\
N -- N -- N refs/changes/13/46213/6 (c8545fb05)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1985 -----------------------------------------------
3 files changed, 3233 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/13/46213/5
in repository toolchain/jenkins-scripts.
discards cc1dd9c05 round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 7298d0ccb round-robin.sh: Move testresults2jenkins.sh to ABE
adds c8545fb05 round-robin.sh: Move testresults2jenkins.sh to ABE
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 (cc1dd9c05)
\
N -- N -- N refs/changes/13/46213/5 (c8545fb05)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1984 -----------------------------------------------
3 files changed, 3232 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/13/46213/4
in repository toolchain/jenkins-scripts.
discards 9f9a2ab9f round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 7298d0ccb round-robin.sh: Move testresults2jenkins.sh to ABE
adds c8545fb05 round-robin.sh: Move testresults2jenkins.sh to ABE
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 (9f9a2ab9f)
\
N -- N -- N refs/changes/13/46213/4 (c8545fb05)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1982 -----------------------------------------------
3 files changed, 3230 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/13/46213/3
in repository toolchain/jenkins-scripts.
discards dc511f9eb round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 7298d0ccb round-robin.sh: Move testresults2jenkins.sh to ABE
adds c8545fb05 round-robin.sh: Move testresults2jenkins.sh to ABE
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 (dc511f9eb)
\
N -- N -- N refs/changes/13/46213/3 (c8545fb05)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1972 -----------------------------------------------
3 files changed, 3220 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/13/46213/2
in repository toolchain/jenkins-scripts.
discards 5935585e1 round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 3637f7938 round-robin.sh (reset_artifacts): Generate README.txt
new bde1942cf round-robin.sh (reset_artifacts): Generate README.txt
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 (5935585e1)
\
N -- N -- N refs/changes/13/46213/2 (bde1942cf)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1972 -----------------------------------------------
3 files changed, 3220 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/13/46213/1
in repository toolchain/jenkins-scripts.
discards 3837b9097 round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 3637f7938 round-robin.sh (reset_artifacts): Generate README.txt
new bde1942cf round-robin.sh (reset_artifacts): Generate README.txt
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 (3837b9097)
\
N -- N -- N refs/changes/13/46213/1 (bde1942cf)
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 | 567 --------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 1972 -----------------------------------------------
3 files changed, 3220 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/13/46013/2
in repository toolchain/jenkins-scripts.
discards a8859dd25 downstream_patches/llvm-vect-metric.diff: Updated to follow llvm
adds 6daddfa17 downstream_patches/llvm-vect-metric.diff: Updated to follow llvm
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 (a8859dd25)
\
N -- N -- N refs/changes/13/46013/2 (6daddfa17)
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/13/46013/1
in repository toolchain/jenkins-scripts.
discards 87512140c downstream_patches/llvm-vect-metric.diff: Updated to follow llvm
new fe3cd1088 downstream_patches/llvm-vect-metric.diff: Updated to follow llvm
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 (87512140c)
\
N -- N -- N refs/changes/13/46013/1 (fe3cd1088)
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/13/45713/2
in repository toolchain/jenkins-scripts.
discards 01a6434e3 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
adds d01608255 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
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 (01a6434e3)
\
N -- N -- N refs/changes/13/45713/2 (d01608255)
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.