The behaviour is different on my laptop though. Test doesn't hang, but it fails (both on master and with 17234). So, as Pranith suggested offline, marking it bad won't help as even bad tests are run by build system (and they might hang). Is removing the test only way?
On Wed, May 10, 2017 at 3:49 PM, Raghavendra G <raghavendra@xxxxxxxxxxx> wrote:
The same test is causing failures for [1] too. On checking it failed on master too. I've submitted a patch [2] to mark it as failure
[1] https://review.gluster.org/#/c/15036
[2] https://review.gluster.org/#/c/17234/ --On Tue, May 9, 2017 at 11:47 PM, Shyam <srangana@xxxxxxxxxx> wrote: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-Februa (see (1) in the mail)ry/052158.html
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
Raghavendra G
--
Raghavendra G
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
