[JIRA] (OVIRT-1965) Add failure details to CQ messages

Sunday, 8 April 2018

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 &ndash; 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 &ndash; 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>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)</p>

------------=_1523193258-16742-109--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011