autobuild[sn-devel-184]: intermittent test failure detected

autobuild autobuild at samba.org
Mon Apr 1 15:46:14 UTC 2019


The autobuild test system (on sn-devel-184) has detected an intermittent failing test in 
the current master tree.

The autobuild log of the failure is available here:

   https://git.samba.org/autobuild.flakey.sn-devel-184/2019-04-01-1546/flakey.log

The failure seems to be in the "samba-nt4" suite, whose build logs are available here:

   https://git.samba.org/autobuild.flakey.sn-devel-184/2019-04-01-1546/samba-nt4.stderr
   https://git.samba.org/autobuild.flakey.sn-devel-184/2019-04-01-1546/samba-nt4.stdout
  
The top commit at the time of the failure was:

commit f1a1c300e192d43f5c9faf9450ffbf16341a2661
Author: Martin Schwenke <martin at meltin.net>
Date:   Tue Mar 26 14:15:33 2019 +1100

    ctdb-scripts: Do not "correct" number of nfsd threads when it is 0
    
    While 0 may indicate that all threads have exited after being stuck,
    it may also indicate that nfsd should not be running due to being shut
    down.
    
    BUG: https://bugzilla.samba.org/show_bug.cgi?id=13860
    
    Signed-off-by: Martin Schwenke <martin at meltin.net>
    Reviewed-by: Amitay Isaacs <amitay at samba.org>
    
    Autobuild-User(master): Martin Schwenke <martins at samba.org>
    Autobuild-Date(master): Sun Mar 31 11:47:44 UTC 2019 on sn-devel-144

and the last 50 lines of the stdout log were:

[192(1095)/588 at 13m34s] samba3.raw.seek(nt4_dc)
[193(1096)/588 at 13m34s] samba3.raw.sfileinfo.bug(nt4_dc)
[194(1096)/588 at 13m34s] samba3.raw.streams(nt4_dc)
[195(1109)/588 at 13m39s] samba3.raw.unlink(nt4_dc)
[196(1112)/588 at 13m40s] samba3.raw.write(nt4_dc)
[197(1116)/588 at 13m40s] samba3.raw.samba3hide(nt4_dc)
[198(1117)/588 at 13m41s] samba3.raw.samba3badpath(nt4_dc)
[199(1118)/588 at 13m41s] samba3.raw.sfileinfo.rename(nt4_dc)
[200(1119)/588 at 13m42s] samba3.raw.session plain(nt4_dc)
[201(1121)/588 at 13m42s] samba3.raw.session enc(nt4_dc)
[202(1123)/588 at 13m42s] samba3.raw.samba3caseinsensitive(nt4_dc)
[203(1124)/588 at 13m43s] samba3.raw.samba3posixtimedlock(nt4_dc)
[204(1125)/588 at 13m48s] samba3.raw.samba3rootdirfid(nt4_dc)
[205(1126)/588 at 13m48s] samba3.raw.sfileinfo.end-of-file(nt4_dc)
[206(1127)/588 at 13m49s] samba3.raw.samba3checkfsp(nt4_dc)
[207(1128)/588 at 13m49s] samba3.raw.samba3closeerr(nt4_dc)
[208(1129)/588 at 13m49s] samba3.raw.samba3oplocklogoff(nt4_dc)
[209(1130)/588 at 13m50s] samba3.raw.samba3badnameblob(nt4_dc)
[210(1131)/588 at 13m50s] samba3.smb2.getinfo(nt4_dc)
[211(1137)/588 at 13m51s] samba3.smb2.lock aio(nt4_dc)
[212(1158)/588 at 13m53s] samba3.smb2.lock(nt4_dc)
[213(1179)/588 at 13m56s] samba3.smb2.read(nt4_dc)
[214(1183)/588 at 13m56s] samba3.smb2.aio_delay(nt4_dc)
[215(1184)/588 at 14m1s] samba3.smb2.create(nt4_dc)
[216(1197)/588 at 14m2s] samba3.smb2.twrp(nt4_dc)
[217(1197)/588 at 14m2s] samba3.smb2.acls(nt4_dc)
[218(1210)/588 at 14m6s] samba3.smb2.notify(nt4_dc)
smbtorture 4.11.0pre1-DEVELOPERBUILD
Using seed 1554133473
TESTING VALIDITY OF CHANGE NOTIFY REQUEST
UNEXPECTED(failure): samba3.smb2.notify.valid-req(nt4_dc)
REASON: Exception: Exception: (../../source4/torture/smb2/notify.c:163) wrong value for n.out.num_changes  0x2 should be 0x3

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

A summary with detailed information can be found in:
  ./bin/ab/summary
TOP 10 slowest tests
samba3.raw.notify(nt4_dc) -> 105
samba3.raw.search(nt4_dc) -> 56
samba3.blackbox.net.rpc.conf(nt4_dc) -> 55
samba3.base.dir2(nt4_dc) -> 46
samba3.raw.oplock(nt4_dc) -> 45
samba3.blackbox.net.local.conf(nt4_dc:local) -> 37
samba3.raw.lock(nt4_dc) -> 34
samba3.smbtorture_s3.crypt_client.OPLOCK1(nt4_dc) -> 30
samba3.raw.search(nt4_dc) -> 18
samba3.base.lock(nt4_dc) -> 17
ERROR: test failed with exit code 1
Makefile:16: recipe for target 'test' failed



More information about the samba-cvs mailing list