On Wed, May 17, 2017 at 4:34 PM, Ravishankar N <ravishan...@redhat.com> wrote:
> On 05/17/2017 04:09 PM, Pranith Kumar Karampuri wrote: > > karthik, Ravi, > What is the plan to bring it back? Did you guys find RC for the > failure? > > Are you referring to gfid-mismatch-resolution-with-fav-child-policy.t? I > already mentioned the RCA in the patch I linked to earlier in this thread? > Ah! missed that. Thanks. We can also use self-heald to do the healing and verify that heals were performed correctly. But it is fine to wait for karthik's next patch. > > On Mon, May 15, 2017 at 10:52 AM, Ravishankar N <ravishan...@redhat.com> > wrote: > >> On 05/12/2017 03:33 PM, Atin Mukherjee wrote: >> >> tests/basic/afr/add-brick-self-heal.t >> <http://git.gluster.org/cgit/glusterfs.git/tree/tests/basic/afr/add-brick-self-heal.t> >> is the 2nd in the list. >> >> >> All failures (https://fstat.gluster.org/weeks/1/failure/2) are in netbsd >> and looks like an issue with the slaves. >> Most of the runs have this error: >> >> [07:29:32] Running tests in file ./tests/basic/afr/add-brick-self-heal.t >> volume create: patchy: failed: Host nbslave70.cloud.gluster.org is not in >> 'Peer in Cluster' state >> >> >> Not investigating the .t itself any further. -Ravi >> _______________________________________________ Gluster-devel mailing >> list Gluster-devel@gluster.org http://lists.gluster.org/mailm >> an/listinfo/gluster-devel > > -- > Pranith > > -- Pranith
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
