Description of problem: 15:51:02 [15:51:05] Running tests in file ./tests/bugs/ec/bug-1236065.t 15:53:35 ./tests/bugs/ec/bug-1236065.t .. 15:53:35 1..41 15:53:35 ok 1, LINENUM:28 15:53:35 ok 2, LINENUM:29 15:53:35 ok 3, LINENUM:30 15:53:35 ok 4, LINENUM:31 15:53:35 ok 5, LINENUM:32 15:53:35 ok 6, LINENUM:33 15:53:35 ok 7, LINENUM:36 15:53:35 ok 8, LINENUM:39 15:53:35 ok 9, LINENUM:42 15:53:35 ok 10, LINENUM:43 15:53:35 ok 11, LINENUM:44 15:53:35 ok 12, LINENUM:46 15:53:35 ok 13, LINENUM:47 15:53:35 ok 14, LINENUM:50 15:53:35 ok 15, LINENUM:51 15:53:35 ok 16, LINENUM:54 15:53:35 ok 17, LINENUM:55 15:53:35 ok 18, LINENUM:56 15:53:35 ok 19, LINENUM:58 15:53:35 ok 20, LINENUM:59 15:53:35 ok 21, LINENUM:62 15:53:35 ok 22, LINENUM:63 15:53:35 ok 23, LINENUM:64 15:53:35 ok 24, LINENUM:66 15:53:35 ok 25, LINENUM:67 15:53:35 ok 26, LINENUM:69 15:53:35 ok 27, LINENUM:72 15:53:35 ok 28, LINENUM:73 15:53:35 ok 29, LINENUM:76 15:53:35 ok 30, LINENUM:77 15:53:35 not ok 31 Got "105" instead of "^0$", LINENUM:78 15:53:35 FAILED COMMAND: ^0$ get_pending_heal_count patchy 15:53:35 ok 32, LINENUM:80 15:53:35 ok 33, LINENUM:81 15:53:35 ok 34, LINENUM:83 15:53:35 ok 35, LINENUM:84 15:53:35 ok 36, LINENUM:85 15:53:35 ok 37, LINENUM:86 15:53:35 ok 38, LINENUM:90 15:53:35 ok 39, LINENUM:91 15:53:35 ok 40, LINENUM:92 15:53:35 ok 41, LINENUM:93 15:53:35 Failed 1/41 subtests Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20685 (tests: Make sure bricks are connected to shd before triggering heal) posted (#1) for review on master by Pranith Kumar Karampuri
Patch abandoned.
Noticed that this is not failing in recent times. Should we close it? If not would like to consider focusing on this.
(In reply to Amar Tumballi from comment #3) > Noticed that this is not failing in recent times. Should we close it? If not > would like to consider focusing on this. It is a race, so may not always happen. I will take this up.
This bug is moved to https://github.com/gluster/glusterfs/issues/984, and will be tracked there from now on. Visit GitHub issues URL for further details