[JIRA] (OVIRT-1965) Add failure details to CQ messages
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1523193258-16742-109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1965:
-----------------------------------
Summary: Add failure details to CQ messages
Key: OVIRT-1965
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra
In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include:
# The names of the OST suits that failed
# The OST tests that failed
# If it was a build failure rather then an OST failure
# If it was possible to detect - the particular change(s) that caused failure.
#if its possible to tell - if its an infra issue or a code regression
To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs - possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed).
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1523193258-16742-109
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1965:</h3>
<pre> Summary: Add failure details to CQ messages
Key: OVIRT-1965
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra</pre>
<p>In order to streamline the process for debugging CQ issues, we should have more failure details added to the messages it sends. Those details should include:</p>
<p># The names of the OST suits that failed # The OST tests that failed # If it was a build failure rather then an OST failure # If it was possible to detect – the particular change(s) that caused failure.</p>
<pre>#if its possible to tell - if its an infra issue or a code regression</pre>
<p>To implement this we would need at the very least a richer interface for passing information between the CQ tester and the and manager jobs – possibly some kind of a structured data file passed around. We may also need a richer interface to OST itself (to tell which test failed) and perhaps even to the build jobs (to tell why the build failed).</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1523193258-16742-109--
7 years
[JIRA] (OVIRT-1964) Add reply-to header to CQ emails
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1523190798-14707-109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1964:
-----------------------------------
Summary: Add reply-to header to CQ emails
Key: OVIRT-1964
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1964
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra
Priority: Low
The "From" header for emails we get from OST points to a non-existent email address. This causes issues when trying to reply on those messages.
We should set a reply-to header that points to a working ML.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1523190798-14707-109
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1964:</h3>
<pre> Summary: Add reply-to header to CQ emails
Key: OVIRT-1964
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1964
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Change Queue
Reporter: Barak Korren
Assignee: infra
Priority: Low</pre>
<p>The “From” header for emails we get from OST points to a non-existent email address. This causes issues when trying to reply on those messages.</p>
<p>We should set a reply-to header that points to a working ML.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1523190798-14707-109--
7 years
[JIRA] (OVIRT-1963) Nicer UI for OST manual job
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1523190173-17372-109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1963:
--------------------------------
Epic Link: OVIRT-400
> Nicer UI for OST manual job
> ----------------------------
>
> Key: OVIRT-1963
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST Manual job
> Reporter: Barak Korren
> Assignee: infra
> Labels: first_time_task
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1523190173-17372-109
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren updated OVIRT-1963:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Nicer UI for OST manual job</h3>
<pre> Key: OVIRT-1963
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: OST Manual job
Reporter: Barak Korren
Assignee: infra
Labels: first_time_task</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1523190173-17372-109--
7 years
[JIRA] (OVIRT-1963) Nicer UI for OST manual job
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1523190173-25549-170
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Barak Korren created OVIRT-1963:
-----------------------------------
Summary: Nicer UI for OST manual job
Key: OVIRT-1963
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: OST Manual job
Reporter: Barak Korren
Assignee: infra
Make the following details shown in the builds list of the OST manual job so that finding a particular build in the builds list is easier:
# The person who triggered the build
# The suit that was run
# The amount of URLs passed into extra-sources, and if possible - the name of the project whose modified packages were included.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1523190173-25549-170
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Barak Korren created OVIRT-1963:</h3>
<pre> Summary: Nicer UI for OST manual job
Key: OVIRT-1963
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: OST Manual job
Reporter: Barak Korren
Assignee: infra</pre>
<p>Make the following details shown in the builds list of the OST manual job so that finding a particular build in the builds list is easier: # The person who triggered the build # The suit that was run # The amount of URLs passed into extra-sources, and if possible – the name of the project whose modified packages were included.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1523190173-25549-170--
7 years
Re: oVirt mirrror broken
by Barak Korren
On 8 April 2018 at 14:39, Rabin Yasharzadehe <rabin(a)isoc.org.il> wrote:
> Hello Barak,
>
> We disabled the sync for oVirt, as it seems it cussed problems.
> I don't have all the detail yet, but is seems to cussed other sync jobs to
> fail/hang.
>
> I'm re-enabling the sync back, and we will investigate this further.
>
> PS.
>
> right now we are syncing from resources.ovirt.org, which is very slow,
> is there any other mirror we can get faster sync speeds?
>
resources is the root repo, but sine released packages are signed
anyway, it should be safe to sync from the other mirrors listed at:
https://www.ovirt.org/develop/infra/repository-mirrors/
I don't know if any of them are exposing rsync though.
Evgheni, can we do something to debug why sync speed for ISOC is so slow?
7 years
