summaryrefslogtreecommitdiff
path: root/selftest/knownfail.d
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2019-12-03 21:33:28 +0100
committerJeremy Allison <jra@samba.org>2019-12-08 20:24:32 +0000
commit8435128582adf81a18e9d929970074d4f2326d20 (patch)
treefc1349a68ddffea4daf264bbcb9d4ce958e5fb62 /selftest/knownfail.d
parentf3802023feb9e5dfa82d2174437b7576470f575b (diff)
downloadsamba-8435128582adf81a18e9d929970074d4f2326d20.tar.gz
smbd: Test cleanup of disconnected durable handle records
Right now this panics the scavenger daemon, preventing it from doing its work. The reopen we expect to fail with NT_STATUS_OBJECT_NAME_NOT_FOUND thus succeeds. I know that we should more precisely detect the scavenger crash and with Jeremy's pattern in 46899ecf836 this would be possible. However, this is C code right now, and scanning the logfile for the panic is more I have time for right now. The test successfully indicates failure, as the next commit will show. Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'selftest/knownfail.d')
-rw-r--r--selftest/knownfail.d/durable_v2_delay_msec1
1 files changed, 1 insertions, 0 deletions
diff --git a/selftest/knownfail.d/durable_v2_delay_msec b/selftest/knownfail.d/durable_v2_delay_msec
new file mode 100644
index 00000000000..3686d38a95c
--- /dev/null
+++ b/selftest/knownfail.d/durable_v2_delay_msec
@@ -0,0 +1 @@
+^samba3.smb2.durable-v2-delay.durable_v2_reconnect_delay_msec