s4-test: SMB2 oplocks in s4 are a mess
authorAndrew Tridgell <tridge@samba.org>
Sun, 18 Oct 2009 04:57:21 +0000 (15:57 +1100)
committerAndrew Tridgell <tridge@samba.org>
Sun, 18 Oct 2009 04:57:21 +0000 (15:57 +1100)
I don't have time to fix these right now, and as we don't advertise
SMB2 by default I'll mark it as a known failure till we start enabling
SMB2 by default.

source4/selftest/knownfail

index 5061171d1e3b34d40656b3758a0664d337d9210a..a9192be6e621416b074ffe5681170735a718bbd4 100644 (file)
@@ -63,3 +63,4 @@ samba4.ntvfs.cifs.base.createx_access
 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