]
Eyal Edri commented on OVIRT-2054:
----------------------------------
I want to start a new policy of closing tickets if we don't get answers for 2 weeks or
the issue isn't happening for 2 weeks.
Otherwise we'll be swamped with tickets.
If a race happens again, you can search for it in JIRA with ost_race to check if it
happened in the past before opening a new ticket.
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
Labels: ost_failures, ost_race
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?