The immediate cause of this failure is that we merged the timeout patch
which gives each test 200 seconds to finish. This test and another one
takes over 200 seconds on regression nodes.

I have a patch up to change the timeout
https://review.gluster.org/#/c/19605/1

However, tests/bugs/rpc/bug-921072.t taking 897 seconds is in itself an
abnormality and is worth looking into.

On Wed, Feb 21, 2018 at 7:47 AM, Atin Mukherjee <amukh...@redhat.com> wrote:

>
>
> *https://build.gluster.org/job/centos7-regression/15/consoleFull 
> <https://build.gluster.org/job/centos7-regression/15/consoleFull>20:24:36* 
> [20:24:39] Running tests in file ./tests/bugs/rpc/bug-921072.t*20:27:56* 
> ./tests/bugs/rpc/bug-921072.t timed out after 200 seconds*20:27:56* 
> ./tests/bugs/rpc/bug-921072.t: bad status 124
>
> This is just one of the instances, but I have seen this test failing in last 
> 3-4 days at least 10 times.
>
> Unfortunately, it doesn't look like the regression actually passes in 
> mainline for any of the patches atm.
>
>
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
nigelb
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Reply via email to