Description of problem:
Some tests which are failing regularly are:
* ./tests/basic/afr/arbiter-mount.t (if NFS is not available).
* ./tests/basic/afr/tarissue.t - randomly
* ./tests/bugs/gfapi/bug-1319374-THIS-crash.t - fails in distributed, and LCOV tests.
There are more but the above are more common suspects:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. send a patch, run regression.
One of these tests would fail.
No tests should fail.
We should have test cases which are specific, and would as predictably as possible. Mark the tests as bad and debug them separately not blocking the development of the master branch.
Blocking other patches from getting in, we would be slowing down a lot in these tests.
> Blocking other patches from getting in, we would be slowing down a lot in these tests.
Correction: We would be slowing down the project's development if we have unstable tests.
REVIEW: https://review.gluster.org/22940 (tests: mark some tests as KNOWN_ISSUE) posted (#1) for review on master by Amar Tumballi
./tests/basic/distribute/non-root-unlink-stale-linkto.t is also failing frequently when creating user.
(In reply to Deepshikha khandelwal from comment #3)
> ./tests/basic/distribute/non-root-unlink-stale-linkto.t is also failing
> frequently when creating user.
The test is not unstable. Gluster has no control over the useradd. We need to figure out what is going wrong on the regression machines.
./tests/bugs/rpc/bug-954057.t needed a retry.
REVIEW: https://review.gluster.org/22949 (test: Fix spurious failure in bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t) posted (#1) for review on master by MOHIT AGRAWAL