I think this should be disabled for now.
See past context here [1] [2], I guess this not being reported as a
failure is causing the attention lapse.
[1] http://lists.gluster.org/pipermail/gluster-devel/2017-March/052287.html
[2]
http://lists.gluster.org/pipermail/gluster-devel/2017-February/052158.html
(see (1) in the mail)
On 05/09/2017 01:50 PM, Jeff Darcy wrote:
After seeing this hang with multiplexing enabled yesterday, I saw it
hang a test for a completely unrelated patch
(https://review.gluster.org/17200) without multiplexing. Does anyone
object to disabling this test while it's debugged?
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel
