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:
./tests/bugs/snapshot/bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t
./tests/bugs/gfapi/bug-1319374-THIS-crash.t
./tests/basic/all_squash.t
./tests/basic/ec/nfs.t
./tests/00-geo-rep/00-georep-verify-setup.t
./tests/basic/quota-rename.t
./tests/basic/volume-snapshot-clone.t
Version-Release number of selected component (if applicable):
master
How reproducible:
>50%
Steps to Reproduce:
1. send a patch, run regression.
Actual results:
One of these tests would fail.
Expected results:
No tests should fail.
Additional info:
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
Comment 3Deepshikha khandelwal
2019-06-25 13:05:16 UTC
./tests/basic/distribute/non-root-unlink-stale-linkto.t is also failing frequently when creating user.
Comment 4Nithya Balachandran
2019-06-25 13:19:02 UTC
(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.
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
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: ./tests/bugs/snapshot/bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t ./tests/bugs/gfapi/bug-1319374-THIS-crash.t ./tests/basic/all_squash.t ./tests/basic/ec/nfs.t ./tests/00-geo-rep/00-georep-verify-setup.t ./tests/basic/quota-rename.t ./tests/basic/volume-snapshot-clone.t Version-Release number of selected component (if applicable): master How reproducible: >50% Steps to Reproduce: 1. send a patch, run regression. Actual results: One of these tests would fail. Expected results: No tests should fail. Additional info: 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.