[
https://ovirt-jira.atlassian.net/browse/OVIRT-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36522#comment-36522
]
eyal edri commented on OVIRT-2015:
----------------------------------
CQ can also fail on OST test change, which is not (yet) a CQ object, you have
to take that into account when debugging failures.
so I'm not sure this is a real issue. [[email protected]]
> CQ marks two different changes in two different projects as cause of failure
> - both are not the cause
> -----------------------------------------------------------------------------------------------------
>
> Key: OVIRT-2015
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2015
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: CQ_false_report
>
> we have what seems to be a code regression in deploy ovn on upgrade suite:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/artifact/exported-artifacts/upgrade-from-release-suit-master-el7/test_logs/upgrade-from-release-suite-master/post-001_initialize_engine.py/
> The failure caused failure in two different projects otopi+imgbased:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7492/
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7488/
> CQ marked a change in each of the projects as the cause of failure:
> Otopi:
> For further details about the change see:
> https://gerrit.ovirt.org/#/c/88930/2
> imgbase;
> For further details about the change see:
> https://gerrit.ovirt.org/#/c/90692/43
> Since the cause of failure is the same for these two projects and the changes
> themselves do not seem like they can be the cause of failure I am reporting
> this ticket for further investigation.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100083)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
