[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1965:
--------------------------------
    Epic Link: OVIRT-2185  (was: OVIRT-400)

> 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#100087)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/LW44KV7FLE7HDQOWDSDQ4ZY4CTFZ6XS2/

Reply via email to