Summary: false change reported since package is not deployed on ost Key: OVIRT-2054 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra
Change 91507,1 (ovirt-engine-sdk-java) is probably the reason behind recent system test failures in the “ovirt-master” change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed.
For further details about the change see: https://gerrit.ovirt.org/#/c/91507/1
For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/
The package is not deployed on OST so it could not have been the reason for failure. + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change – hence its false report.
Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere?
— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)