The autobuild test system has detected an intermittent failing test in the current master tree.
The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2015-10-26-0604/flakey.log The samba build logs are available here: http://git.samba.org/autobuild.flakey/2015-10-26-0604/samba.stderr http://git.samba.org/autobuild.flakey/2015-10-26-0604/samba.stdout The top commit at the time of the failure was: commit 0a924d13cf4bb570cce3955cf0de9d8678b37dbe Author: Volker Lendecke <v...@samba.org> Date: Tue Oct 6 16:10:43 2015 +0200 smbd: Send SMB2 oplock breaks unencrypted This is not what Windows server does, but it seems that Windows clients expect. Windows->Windows never runs into this issue, because an encryption-enabled SMB3 connection will always use leases, and lease breaks *are* unencrypted... You can reproduce the issue Windows->Windows by disabling leases on the Windows server. Disable leases using the registry key: HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\DisableLeasing Dochelp confirmed that this is a valid workaround for Windows clients dropping encrypted oplock breaks. BUG: https://bugzilla.samba.org/show_bug.cgi?id=11570 Signed-off-by: Volker Lendecke <v...@samba.org> Reviewed-by: Stefan Metzmacher <me...@samba.org> Autobuild-User(master): Jeremy Allison <j...@samba.org> Autobuild-Date(master): Sat Oct 24 05:01:32 CEST 2015 on sn-devel-104
