[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36562#comment-36562 ]
Arik is investigating the failure and he thinks he knows the cause. I looked at CQ to try and see what the issue is and I can see 3 changes tested (all merged by Arik) and all 3 failed on the same issue. The first change ran here:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/
and it was marked as failed due to https://gerrit.ovirt.org/#/c/91084/1 which I think was not fixed yet. hence, all other failures were marked with https://gerrit.ovirt.org/#/c/91084/1 in CQ.
I asked Arik to let me know if he can pin point the failure to a specific patch but I am 99% sure it is the first one that failed.
CQ reporting wrong change as root cause
Key: OVIRT-2021 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2021 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra[CQ]: 91188, 2 (ovirt-engine) failed “ovirt-master” system tests, but isn't the failure root cause For further details about the change see: https://gerrit.ovirt.org/#/c/91188/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91084/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7552/ The failure is a time out which was caused by a NPE (which is a real bug). CQ reported the failure as related to JSONRPC which after discussing it with the developers has nothing to do with the NPE.
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100084)