[ https://ovirt-jira.atlassian.net/browse/OVIRT-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36570#comment-36570 ]
we can close this ticket. the issue was this change: https://gerrit.ovirt.org/#/c/91038/ which failed on build-artifacts (so CQ did not even start).
it was merged on May 9th We had 3 other issues last week:
centos changing the repos for 7.5
broken packages (vdsm-jsonrpc)
ost broken due to upgrade patch
our first failure in cq detecting this change was:
Build #7552 [1: 91188,2 (ovirt-engine)] (May 13, 2018 3:52:53 PM)
but ovirt-engine was continuously broken due to different issues and CQ was behaving as expected.
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#100085)