Re: DIR1 samba3 test flakey in autobuild

On Fri, 2012-05-18 at 11:14 +1000, Andrew Bartlett wrote:
> After your comments on IRC, I've look looked over the last 3 flakey
> auto-builds, and the reason we are having trouble appears to be:
> 
> UNEXPECTED(failure):
> samba3.smbtorture_s3.plain(s3dc).DIR1.smbtorture(s3dc)
> REASON: _StringException: _StringException: using seed 1337098205
> host=127.0.0.2 share=tmp user=autobuild myname=sn-devel-104
> Running DIR1
> starting directory test
> num_seen = 0
> num_seen = 0
> num_seen = 0
> tdis failed (NT_STATUS_CONNECTION_DISCONNECTED)
> finished dirtest1
> TEST DIR1 FAILED!
> DIR1 took 7.43293 secs
> 
> UNEXPECTED(failure): samba3.smbtorture_s3.crypt(s3dc).DIR1.smbtorture(s3dc)
> REASON: _StringException: _StringException: using seed 1337170149
> host=127.0.0.2 share=tmp user=autobuild myname=sn-devel-104
> Running DIR1
> starting directory test
> cli_credentials_set_ccache is unimplemented in the autoconf build
> num_seen = 2002
> num_seen = 1002
> num_seen = 0
> tdis failed (NT_STATUS_CONNECTION_DISCONNECTED)
> finished dirtest1
> TEST DIR1 FAILED!
> DIR1 took 18.0362 secs
> 
> Naturally, the question is: why would the connection suddenly be
> disconnected, right at the end of the test?

The other one that has hit me and registered in the flaky autobuild is:
[310/1511 in 17m10s] samba3.base.lock(s3dc)
Testing 32 bit offset rangesUnable to setup \locktest - NT_STATUS_DELETE_PENDING
UNEXPECTED(error): samba3.base.lock.LOCK3(s3dc)
REASON: _StringException: _StringException: Unknown error/failure. Missing torture_fail() or
torture_assert_*() call?

FAILED (0 failures, 1 errors and 0 unexpected successes in 0 testsuites)

Andrew Bartlett
--

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org