From 5d3659a8819bee6c5337c21f1148bc6658f7bb0a Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Sun, 18 Oct 2009 15:57:21 +1100 Subject: s4-test: SMB2 oplocks in s4 are a mess 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 | 1 + 1 file changed, 1 insertion(+) (limited to 'source4/selftest/knownfail') diff --git a/source4/selftest/knownfail b/source4/selftest/knownfail index 5061171d1e..a9192be6e6 100644 --- a/source4/selftest/knownfail +++ b/source4/selftest/knownfail @@ -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 -- cgit