<div dir="ltr"><div dir="ltr">Sent <a href="https://review.gluster.org/c/glusterfs/+/21889">https://review.gluster.org/c/glusterfs/+/21889</a> to fix the original issue.</div><div dir="ltr"><br></div><div>-Krutika<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 5, 2018 at 10:58 AM Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div> We can't afford to keep a bad test hanging for more than a day which penalizes other fixes to be blocked (I see atleast 4-5 more patches failed on the same test today). I thought we already had a rule to mark a test bad at earliest in such occurrences. Not sure why we haven't done that yet. In any case, I have marked this test as bad through <a href="https://review.gluster.org/#/c/glusterfs/+/21800/" target="_blank">https://review.gluster.org/#/c/glusterfs/+/21800/</a> , please review and merge.<br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 4, 2018 at 7:46 PM Shyam Ranganathan <<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Test: ./tests/bugs/shard/zero-flag.t<br>
<br>
Runs:<br>
- <a href="https://build.gluster.org/job/centos7-regression/3942/console" rel="noreferrer" target="_blank">https://build.gluster.org/job/centos7-regression/3942/console</a><br>
- <a href="https://build.gluster.org/job/centos7-regression/3941/console" rel="noreferrer" target="_blank">https://build.gluster.org/job/centos7-regression/3941/console</a><br>
- <a href="https://build.gluster.org/job/centos7-regression/3938/console" rel="noreferrer" target="_blank">https://build.gluster.org/job/centos7-regression/3938/console</a><br>
<br>
Failures seem to occur at common points across the tests like so,<br>
<br>
09:52:34 stat: missing operand<br>
09:52:34 Try 'stat --help' for more information.<br>
09:52:34 not ok 17 Got "" instead of "2097152", LINENUM:40<br>
09:52:34 FAILED COMMAND: 2097152 echo<br>
<br>
09:52:34 stat: cannot stat<br>
‘/d/backends/patchy*/.shard/41fed5c6-636e-44d6-b6ed-068b941843cd.2’: No<br>
such file or directory<br>
09:52:34 not ok 27 , LINENUM:64<br>
09:52:34 FAILED COMMAND: stat<br>
/d/backends/patchy*/.shard/41fed5c6-636e-44d6-b6ed-068b941843cd.2<br>
09:52:34 stat: missing operand<br>
09:52:34 Try 'stat --help' for more information.<br>
09:52:34 not ok 28 Got "" instead of "1048602", LINENUM:66<br>
09:52:34 FAILED COMMAND: 1048602 echo<br>
<br>
Krutika, is this something you are already chasing down?<br>
<br>
Thanks,<br>
Shyam<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div>
</blockquote></div>