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<span></span>?<div><br></div><div>Raghavendra T - any more findings?<br><br>On Friday 19 August 2016, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1368421" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1368421</a><br><br></div><div>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.<br><br></div><div>I'd request the feature owner/maintainer to have a look at it asap.<br></div><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><br></div>--Atin<br></div></div>
</div></div>
</blockquote></div><br><br>-- <br>--Atin<br>