On Thu, Dec 22, 2016 at 5:59 PM, Leon Goldberg <lgoldber(a)redhat.com> wrote:
So it's not about the added network tests (these were added in
the one I've
mentioned, the one who had successful runs after being merged), and I don't
see how the patch you've mentioned breaks anything (as it merely moves
pieces around).
I could of course be wrong entirely and there's something I'm missing about
the patch you're claiming is the guilty one, but it won't be about the
network tests either way.
If it's then not about the network tests, then my immediate suspicion is
that the problem lies somewhere else and isn't in either of the patches. I
am far from able to prove this either way, though, so if reverting the patch
you've mentioned somehow fixes check-merged, then it is of course fine by
me.
On Thu, Dec 22, 2016 at 5:45 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote:
>
>
>
> On Thu, Dec 22, 2016 at 5:39 PM, Leon Goldberg <lgoldber(a)redhat.com>
> wrote:
>>
>> Doesn't seem related; the patch does nothing but move pieces around.
>>
>> Judging by the title I guess you're referring to
>>
https://gerrit.ovirt.org/#/c/67787/ ?
>
>
>
> no.. you can see that after this patch it used to work (check the jobs
> after the merge)
> so something in
https://gerrit.ovirt.org/#/c/68078/ broke it
>
>>
>>
>> On Thu, Dec 22, 2016 at 5:14 PM, Yaniv Bronheim <ybronhei(a)redhat.com>
>> wrote:
>>>
>>> Hi guys and Leon,
>>>
>>>
https://gerrit.ovirt.org/#/c/68078/ broke the check-merged job with
>>> really tough exception:
>>>
>>> 15:23:34 sh: [17766: 1 (255)] tcsetattr: Inappropriate ioctl for device
>>> 15:23:34 Took 2586 seconds
>>> 15:23:34 Slave went offline during the build
>>> 15:23:34 ERROR: Connection was broken: java.io.IOException: Unexpected
Maybe the problem is few line above this. Could Jenkins simply timeout?
Ran 44 tests in 1752.270s
OK
+ return 0
sh: [9520: 1 (255)] tcsetattr: Inappropriate ioctl for device
Anyway, a revert is available