[
https://ovirt-jira.atlassian.net/browse/OVIRT-1649?page=com.atlassian.jir...
]
eyal edri commented on OVIRT-1649:
----------------------------------
We are planning to start commenting directly in Gerrit on the relevant
offending patch soon, we were waiting to see how CQ behaves and sending
emails to infra only until now.
However, it looks like it's quite accurate, so we might consider doing it
sooner, though we might also want to wait until we gate also OS changes
before during that.
Nevertheless, I guess we can in the meantime include the patch owner in the
'to' email when sending a report.
Any comments on the current summary? is there something missing in it other
than the patch owner?
On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <
https://www.redhat.com/>
<
https://red.ht/sig> TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
Include summary, owner and component of suspected patch in OST
Failure Report
-----------------------------------------------------------------------------
Key: OVIRT-1649
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1649
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: danken
Assignee: infra
$subject would make it easier and quicker to check if the suspicion is correct.
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)