summaryrefslogtreecommitdiff
path: root/source4/selftest/knownfail
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2009-11-18 08:20:29 +0100
committerStefan Metzmacher <metze@samba.org>2009-11-18 08:24:13 +0100
commitfb685d3a8afed4c14f5e7a17ef58225c2946ed67 (patch)
tree2858a0952dfb7b1a4d04b7d0eb4ccf6f2fe0922c /source4/selftest/knownfail
parentc2a29967ea0395460583edbbb91d04f897fee81d (diff)
downloadsamba-fb685d3a8afed4c14f5e7a17ef58225c2946ed67.tar.gz
samba-fb685d3a8afed4c14f5e7a17ef58225c2946ed67.tar.bz2
samba-fb685d3a8afed4c14f5e7a17ef58225c2946ed67.zip
s4:selftest: mark samba4.smb2.lock.*.VALID-REQUEST as known failure
metze
Diffstat (limited to 'source4/selftest/knownfail')
-rw-r--r--source4/selftest/knownfail1
1 files changed, 1 insertions, 0 deletions
diff --git a/source4/selftest/knownfail b/source4/selftest/knownfail
index 2f757608a1..3694aede1b 100644
--- a/source4/selftest/knownfail
+++ b/source4/selftest/knownfail
@@ -63,3 +63,4 @@ samba4.ntvfs.cifs.base.createx_sharemodes_dir
samba4.ntvfs.cifs.base.maximum_allowed
samba4.base.createx_access # this test is broken for non-administrator users
samba4.smb2.oplock # oplocks in the s4 SMB2 server are a mess
+samba4.smb2.lock.*.VALID-REQUEST # the s4 SMB2 server doesn't check lock ranges