[Gluster-devel] Spurious failures because of nfs and snapshots

[Pranith Kumar Karampuri]

----- Original Message -----
> From: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> To: "Justin Clift" <justin at gluster.org>
> Cc: "Gluster Devel" <gluster-devel at gluster.org>
> Sent: Monday, May 19, 2014 11:20:21 AM
> Subject: Re: [Gluster-devel] Spurious failures because of nfs and snapshots
> 
> 
> 
> ----- Original Message -----
> > From: "Justin Clift" <justin at gluster.org>
> > To: "Pranith Kumar Karampuri" <pkarampu at redhat.com>
> > Cc: "Gluster Devel" <gluster-devel at gluster.org>
> > Sent: Monday, 19 May, 2014 10:41:03 AM
> > Subject: Re: [Gluster-devel] Spurious failures because of nfs and snapshots
> > 
> > On 19/05/2014, at 6:00 AM, Pranith Kumar Karampuri wrote:
> > <snip>
> > > This particular class is eliminated :-). Patch was merged on Friday.
> > 
> > 
> > Excellent.  I've just kicked off 10 instances in Rackspace to each run
> > the regression tests on master head.
> > 
> > Hopefully less than 1/2 of them fail this time.  Has been about 30%
> > pass rate recently. :)
> 
> I am working on one more patch about timeouts at the moment. Will be sending
> it shortly. That should help us manage waiting for timeouts easily.
> With the work kaushal, vijay did for providing logs, core files, we should be
> able to reduce the number of spurious regressions. Because now, we can debug
> them without stopping running of regressions :-).

The patch is now ready for review at http://review.gluster.com/7799. Intention of the patch is to make sure similar events wait for same time for those events to happen. i.e. EXPECT_WITHIN related ones. So next time some event stops completing the action in the expected time-limit and we want to increase the timeout, we only have to change it in one place.

Pranith

> 
> Pranith
> > 
> > + Justin
> > 
> > --
> > Open Source and Standards @ Red Hat
> > 
> > twitter.com/realjustinclift
> > 
> > 
>