This is still bothering us a lot and looks like there is a genuine issue in the code which is making the the process to be hung/deadlocked?
Raghavendra T - any more findings? On Friday 19 August 2016, Atin Mukherjee <amukh...@redhat.com> wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1368421 > > NetBSD regressions are getting aborted very frequently. Apart from the > infra issue related to connectivity (Nigel has started looking into it), > lock_revocation.t is getting hung in such instances which is causing run to > be aborted after 300 minutes. This has already started impacting the > patches to get in which eventually impacts the upcoming release cycles. > > I'd request the feature owner/maintainer to have a look at it asap. > > --Atin > -- --Atin
_______________________________________________ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers
