[
https://ovirt-jira.atlassian.net/browse/OVIRT-1571?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-1571:
-------------------------------------
[~sradco(a)redhat.com] The 1st patchset seems to have been triggered while we had some
communication outage with Gerrit which caused Jenkins to not be able to send responses to
Gerrit, here are the jobs:
http://jenkins.ovirt.org/job/ovirt-engine-metrics_master_check-patch-el7-...
http://jenkins.ovirt.org/job/ovirt-engine-metrics_master_check-patch-fc25...
The 2nd patch set only included a commit message update so it does not trigger CI.
I've re-triggered the jobs manually for now.
[~ederevea] please confirm we had a known Gerrit outage when the 1st patch-set was
submitted (Jul 27 5:02 PM), and link relevant ticket if we did.
Issue with a patch in gerrit
----------------------------
Key: OVIRT-1571
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-1571
Project: oVirt - virtualization made easy
Issue Type: Outage
Components: oVirt CI
Reporter: Shirly Radco
Assignee: infra
Labels: gerrit, standard-ci
Hi,
I have patch
https://gerrit.ovirt.org/#/c/79900/.
I get a gerrit message that I'm not sure what is the issue there.
Also, the check patch was not triggered for this patch.
Please check.
Thank you,
--
SHIRLY RADCO
BI SOFTWARE ENGINEER
Red Hat Israel <
https://www.redhat.com/>
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
--
This message was sent by Atlassian JIRA
(v1000.1154.0#100057)