בתאריך 20 בספט׳ 2017 05:44 PM, "Juan Hernández" כתב:
I am aware of that build failure. The tests of the *Ruby* SDK hang
apparently random in ppc64le environments. I am trying to find out why, but
not making much progress, to be honest.
Meanwhile I wonder why this is a
We just had a second failure which CQ is reporting to be from the same
patch:
failed job:
http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1034/console
if you look at the console output you can see this:
*12:27:15* ovirt-engine-sdk-ruby_4.1_build-artifacts-fc24-ppc64le (122) failed
The http returned 503:
192.168.201.1 - - [20/Sep/2017:05:17:10 -0400] "GET
/ovirt-engine/api/hosts/06b9cdf3-5bcb-4be8-9e11-8ad5123749f0 HTTP/1.1"
200 5249
192.168.201.1 - - [20/Sep/2017:05:17:13 -0400] "GET
/ovirt-engine/api/hosts/06b9cdf3-5bcb-4be8-9e11-8ad5123749f0 HTTP/1.1"
503 299
That SDK patch is for the *Ruby* SDK, which isn't used in OST, so I
think it isn't related.
On 09/20/2017 02:11 PM, Martin Perina wrote:
Ondro, could you please take a look?
On Wed, Sep 20, 2017 at 1:07 PM, Dafna Ron wrote:
Hi,
We have a failure in test
Ondro, could you please take a look?
On Wed, Sep 20, 2017 at 1:07 PM, Dafna Ron wrote:
> Hi,
>
> We have a failure in test post-002_bootstrap.py
>
> from the logs I can see that lago has an unhandled exception from ovirt
> sdk which makes sense since the patch reported on CQ is
Hi,
We have a failure in test post-002_bootstrap.py
from the logs I can see that lago has an unhandled exception from ovirt
sdk which makes sense since the patch reported on CQ is a change to the
sdk.
**
*Link to suspected patches: https://gerrit.ovirt.org/#/c/82022/*
*
Link to Job: