diff options
| author | Brian Behlendorf <[email protected]> | 2022-02-20 19:21:31 -0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2022-02-20 19:21:31 -0800 |
| commit | a5b3fab341b375ecfaea173ba46abe0b6ff218c4 (patch) | |
| tree | 971f8e8eed1883a121507b33d7b8aacb885839e1 /tests/test-runner | |
| parent | 806739f991aa0d3fc5a36989fff8d8ab8fddf78f (diff) | |
ZTS: Retry in import_rewind_config_changed.ksh
As explained by the disclaimer in the test case,
"This test can fail since nothing guarantees that old
MOS blocks aren't overwritten."
This behavior is expected and correct, but results in a
flaky test case which is problematic for the CI. The best
we can do to resolve this is to retry the sub-test which
failed when the MOS blocks have clearly been overwritten.
When testing failures were rare enough that a single retry
should normally be sufficient. However, we allow up to
five for good measure.
Reviewed by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #13119
Diffstat (limited to 'tests/test-runner')
| -rwxr-xr-x | tests/test-runner/bin/zts-report.py.in | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/tests/test-runner/bin/zts-report.py.in b/tests/test-runner/bin/zts-report.py.in index 74a6a1b4d..cdb4fc343 100755 --- a/tests/test-runner/bin/zts-report.py.in +++ b/tests/test-runner/bin/zts-report.py.in @@ -222,8 +222,6 @@ maybe = { 'cli_root/zfs_unshare/setup': ['SKIP', share_reason], 'cli_root/zpool_add/zpool_add_004_pos': ['FAIL', known_reason], 'cli_root/zpool_destroy/zpool_destroy_001_pos': ['SKIP', '6145'], - 'cli_root/zpool_import/import_rewind_config_changed': - ['FAIL', rewind_reason], 'cli_root/zpool_import/zpool_import_missing_003_pos': ['SKIP', '6839'], 'cli_root/zpool_initialize/zpool_initialize_import_export': ['FAIL', '11948'], |