summaryrefslogtreecommitdiffstats
path: root/tests/test-runner
diff options
context:
space:
mode:
authorBrian Behlendorf <[email protected]>2018-10-01 17:15:57 -0700
committerGitHub <[email protected]>2018-10-01 17:15:57 -0700
commit838bd5ff35db04695ba4eadc7fdb2d56ff816ee5 (patch)
tree5a19ae6ebd4021df27e543cbdc0ab5f30962f9b8 /tests/test-runner
parent424fd7c3e080255935646d2beaa2655c116cc37a (diff)
ZTS: Fix snapshot_009_pos, snapshot_010_pos
Mitigate the likelihood of the newly created volumes being busy when the 'zfs destroy -r' is issued by waiting for udev to settle. Since this is not a iron clad fix I've added the test case to the known list of possible failures and referenced issue #7961. Finally, in the case this test does fail fix the cleanup logic so subsequent tests won't incorrectly fail. Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: George Melikov <[email protected]> Reviewed-by: John Kennedy <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes #7961 Closes #7962
Diffstat (limited to 'tests/test-runner')
-rwxr-xr-xtests/test-runner/bin/zts-report.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/test-runner/bin/zts-report.py b/tests/test-runner/bin/zts-report.py
index 2cf2eb941..d4e743a17 100755
--- a/tests/test-runner/bin/zts-report.py
+++ b/tests/test-runner/bin/zts-report.py
@@ -264,6 +264,8 @@ maybe = {
'rsend/rsend_024_pos': ['FAIL', '5665'],
'rsend/send-c_volume': ['FAIL', '6087'],
'snapshot/clone_001_pos': ['FAIL', known_reason],
+ 'snapshot/snapshot_009_pos': ['FAIL', '7961'],
+ 'snapshot/snapshot_010_pos': ['FAIL', '7961'],
'snapused/snapused_004_pos': ['FAIL', '5513'],
'tmpfile/setup': ['SKIP', tmpfile_reason],
'threadsappend/threadsappend_001_pos': ['FAIL', '6136'],