[ovirt-devel] Re: Flaky jsonrpc test? looks like timeout

2019-12-17 Thread Nir Soffer
On Tue, Dec 17, 2019 at 7:37 PM Nir Soffer wrote: > > I had this failure today, that looks like a timeout, based on the test > duration: > > 18.16s call > tests/lib/yajsonrpc/jsonrpcserver_test.py::JsonRpcServerTests::testMethodBadParameters(True) > > Looking at the log it smells like the known

[ovirt-devel] Flaky jsonrpc test? looks like timeout

2019-12-17 Thread Nir Soffer
I had this failure today, that looks like a timeout, based on the test duration: 18.16s call tests/lib/yajsonrpc/jsonrpcserver_test.py::JsonRpcServerTests::testMethodBadParameters(True) Looking at the log it smells like the known race when connecting to server. Also we see: - ERROR

[ovirt-devel] Re: [rhev-devel] Re: New dependency for development environment

2019-12-17 Thread Kaustav Majumder
Thanks Steven. Let me check. On Tue, Dec 17, 2019 at 7:18 PM Steven Rosenberg wrote: > Dear Kaustav Majumder, > > We resolved the issue I had and the symptoms sound similar to what you are > experiencing. > > 1. One needs to have the ansible versions installs from these packages [1] > which

[ovirt-devel] Re: [rhev-devel] Re: New dependency for development environment

2019-12-17 Thread Steven Rosenberg
Dear Kaustav Majumder, We resolved the issue I had and the symptoms sound similar to what you are experiencing. 1. One needs to have the ansible versions installs from these packages [1] which includes ansible-runner 1.3.4 2. If you do ansible-runner --version and you get version 1.0.1 you need

[ovirt-devel] CI system outage

2019-12-17 Thread Evgheni Dereveanchin
Hello everyone, We received several reports of Jenkins jobs not running properly. The reason turned out to be the Jenkins Master which did not start jobs properly. It has been restarted and is working properly now. If you have any jobs that failed or did not start at all today - please

[ovirt-devel] Re: published master engine is 13 days old

2019-12-17 Thread Martin Perina
On Tue, Dec 17, 2019 at 9:55 AM Anton Marchukov wrote: > Hi. > > We do watch those and this one was reported by Dafna though devel list was > not included for some reason (usually we do include it). We strive to > follow up on it daily, but sometimes we lag behind. > > It would be good to send

[ovirt-devel] Re: published master engine is 13 days old

2019-12-17 Thread Anton Marchukov
Hi. We do watch those and this one was reported by Dafna though devel list was not included for some reason (usually we do include it). We strive to follow up on it daily, but sometimes we lag behind. It would be good to send to the patch owner that the system is identified as being a

[ovirt-devel] Re: published master engine is 13 days old

2019-12-17 Thread Yedidyah Bar David
On Tue, Dec 17, 2019 at 10:11 AM Yedidyah Bar David wrote: > > Hi all, > > $subject. [1] has > ovirt-engine-4.4.0-0.0.master.20191204120550.git04d5d05.el7.noarch . > > Tried to look around, and I have a few notes/questions: > > 1. Last successful run of [2] is 3 days old, but apparently it wasn't

[ovirt-devel] published master engine is 13 days old

2019-12-17 Thread Yedidyah Bar David
Hi all, $subject. [1] has ovirt-engine-4.4.0-0.0.master.20191204120550.git04d5d05.el7.noarch . Tried to look around, and I have a few notes/questions: 1. Last successful run of [2] is 3 days old, but apparently it wasn't published. Any idea why? 2. Failed runs of [2] are reported to infra,