diff options
| author | Brian Behlendorf <[email protected]> | 2018-09-13 13:35:09 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2018-09-13 13:35:09 -0700 |
| commit | 92b432139da587c85648ac96dc31ed8c4b5d7b97 (patch) | |
| tree | 4f742ed3d3efbed18431c0fdb5f5bcd5c684628d /tests/test-runner | |
| parent | 733b5722b4fc6e7927ea8a33bef49f7059d91903 (diff) | |
Add removal_resume_export to zts-report.py
Add the removal_resume_export test case to the possible failure
section of the zts-report.py and reference the Github issue. In
the CI environment this test has proven to be unreliable due to
the way it detects the removal thread. This is a flaw in the test
and not device removal so update the result summary accordingly.
Additionally, increase the allowed timeout in an effort to reduce
the observed rate of false positves.
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #7895
Issue #7894
Diffstat (limited to 'tests/test-runner')
| -rwxr-xr-x | tests/test-runner/bin/zts-report.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/test-runner/bin/zts-report.py b/tests/test-runner/bin/zts-report.py index 5747f1422..61cbb54dd 100755 --- a/tests/test-runner/bin/zts-report.py +++ b/tests/test-runner/bin/zts-report.py @@ -256,6 +256,7 @@ maybe = { 'no_space/enospc_002_pos': ['FAIL', enospc_reason], 'projectquota/setup': ['SKIP', exec_reason], 'redundancy/redundancy_004_neg': ['FAIL', '7290'], + 'removal/removal_resume_export': ['FAIL', '7894'], 'reservation/reservation_008_pos': ['FAIL', '7741'], 'reservation/reservation_018_pos': ['FAIL', '5642'], 'rsend/rsend_019_pos': ['FAIL', '6086'], |