ok, I realised you're referring to the message sent manually by the infra-owner, as opposed to the generated message delivered the CQ to the infra-list.

I agree that at the very least the project name should be there, and probably also documented in the OST failure tracking table we maintain.

in "component" I meant ovirt-project. (engine/vdsm/node/...)

This already shows up. Both in the subject line and in the message body.

in "component" I meant ovirt-project. (engine/vdsm/node/...)

Yes - I've asked to have the patch summary line, and its component.

I'm probably not going to implement this, it will become redundant once CQ messages are posted to Gerrit and requires some extensive code changes to keep this information so it is available in time for reporting.

BTW not sure what you mean by "component".

On Thu, Sep 14, 2017 at 3:17 PM, eyal edri (oVirt JIRA) <

Yes - I've asked to have the patch summary line, and its component.

On Thu, Sep 14, 2017 at 3:11 PM, danken (oVirt JIRA) <

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)