<div dir="ltr">The test failure is the flag.<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 21, 2018 at 7:28 PM Sankarshan Mukhopadhyay <<a href="mailto:sankarshan.mukhopadhyay@gmail.com">sankarshan.mukhopadhyay@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jun 21, 2018 at 7:11 PM, Nigel Babu <<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>> wrote:<br>
> I've been seeing two kinds of hangs that are causing this<br>
> * Bad tests that take a lot of time and hang.<br>
<br>
How are such tests flagged for improvements?<br>
<br clear="all"></blockquote></div><div> The test failure is the flag. In the past, these test runs would only be caught after the test has been merged. Now it will up to the test author to debug and bring the test time down to under 4h and not cause hangs.<br></div><div><br></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div></div>