
This change might be the R.C. of a new regression, previous change failed because of an infra issue and a re-test for it passed. Re adding for this change to see if the issue with it re-occurs. Re-add run: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue/5549/ Tester run: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2034/ Note - an ovirt-host change was also added by mistake, so a bisection will probably need to happen before this change is re-tested on its own. On 27 May 2018 at 15:43, oVirt Jenkins <jenkins@ovirt.org> wrote:
A system test invoked by the "ovirt-4.2" change queue including change 91638,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91621,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures.
This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91621,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it.
For further details about the change see: https://gerrit.ovirt.org/#/c/91638/2
For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91621/1
For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2027/ _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted