Description of problem:
The test mentioned in summary is now failing frequently, to unblock the other patches mark it bad for now.
Regression failure links:
REVIEW: https://review.gluster.org/16479 (tests: Mark tests/bitrot/bug-1373520.t bad) posted (#1) for review on master by Atin Mukherjee (email@example.com)
COMMIT: https://review.gluster.org/16479 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Atin Mukherjee <email@example.com>
Date: Mon Jan 30 13:13:54 2017 +0530
tests: Mark tests/bitrot/bug-1373520.t bad
Signed-off-by: Atin Mukherjee <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
Reviewed-by: N Balachandran <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Kotresh HR <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
Although this bug is tracked against mainline, I backported the commit to mark this test as bad in release-3.10 as well. This is to ensure we do not get spurious failures against commits for that branch.
The Bug used to make this change is #1419696
Request any fix to be back ported and the test unblocked as appropriate.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.
glusterfs-3.11.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.