Description of problem:
Marking the 2 said tests in Summary as bad in release-3.10 to prevent spurious failures.
The mainline bugs for the same are #1416689 and #1417540
Fixes for the test case should consider back porting the said fixes to release-3.10 as well, if applicable, or if not remove the bad test lines as appropriate.
REVIEW: https://review.gluster.org/16549 (tests: Marked 2 tests in master that bad, the same in release-3.10) posted (#1) for review on release-3.10 by Shyamsundar Ranganathan (email@example.com)
COMMIT: https://review.gluster.org/16549 committed in release-3.10 by Shyamsundar Ranganathan (firstname.lastname@example.org)
Author: Shyam <email@example.com>
Date: Mon Feb 6 14:05:54 2017 -0500
tests: Marked 2 tests in master that bad, the same in release-3.10
The 2 tests that were marked bad in master are,
The same are marked bad in release-3.10 to prevent any spurious
failures during backporting other commits.
When the failures are analyzed and fixed in master the same would
need to be backported, as applicable, to release-3.10 branch.
Signed-off-by: Shyam <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
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.10.0, please open a new bug report.
glusterfs-3.10.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.