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 https://review.gluster.org/#/c/glusterfs/+/21800/ , please review and merge.
On Tue, Dec 4, 2018 at 7:46 PM Shyam Ranganathan <srangana@xxxxxxxxxx> wrote:
Test: ./tests/bugs/shard/zero-flag.t
Runs:
- https://build.gluster.org/job/centos7-regression/3942/console
- https://build.gluster.org/job/centos7-regression/3941/console
- https://build.gluster.org/job/centos7-regression/3938/console
Failures seem to occur at common points across the tests like so,
09:52:34 stat: missing operand
09:52:34 Try 'stat --help' for more information.
09:52:34 not ok 17 Got "" instead of "2097152", LINENUM:40
09:52:34 FAILED COMMAND: 2097152 echo
09:52:34 stat: cannot stat
‘/d/backends/patchy*/.shard/41fed5c6-636e-44d6-b6ed-068b941843cd.2’: No
such file or directory
09:52:34 not ok 27 , LINENUM:64
09:52:34 FAILED COMMAND: stat
/d/backends/patchy*/.shard/41fed5c6-636e-44d6-b6ed-068b941843cd.2
09:52:34 stat: missing operand
09:52:34 Try 'stat --help' for more information.
09:52:34 not ok 28 Got "" instead of "1048602", LINENUM:66
09:52:34 FAILED COMMAND: 1048602 echo
Krutika, is this something you are already chasing down?
Thanks,
Shyam
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
