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

autobuild autobuild at
Mon Nov 5 05:37:24 UTC 2018

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

The autobuild log of the failure is available here:

The failure seems to be in the "samba-nt4" suite, whose build logs are available here:
The top commit at the time of the failure was:

commit 3338a3e257fa9f285ae639d6ac382e3e234be90e
Author: Tim Beale <timbeale at>
Date:   Tue Oct 30 16:14:33 2018 +1300

    traffic: Machine accounts were generated as critical objects
    Due to the userAccountControl flags we were specifying, the machine
    accounts were all created as critical objects. When trying to populate
    1000s of machine accounts in a DB, this makes replication unnecessarily
    slow (because it has to replicate them all twice).
    This patch changes it so when we're just creating machine accounts for
    the purpose of populating a semi-realistic DB, we jsut use the default
    Note that for the accounts used for traffic-replay, we apparently need
    the existing flags in order for the DC to accept certain requests.
    Signed-off-by: Tim Beale <timbeale at>
    Reviewed-by: Douglas Bagnall <douglas.bagnall at>
    Autobuild-User(master): Tim Beale <timbeale at>
    Autobuild-Date(master): Mon Nov  5 03:43:24 CET 2018 on sn-devel-144

and the last 50 lines of the stdout log were:

[184(1049)/576 at 11m52s] samba3.raw.streams(nt4_dc)
[185(1062)/576 at 11m56s] samba3.raw.unlink(nt4_dc)
[186(1065)/576 at 11m56s] samba3.raw.write(nt4_dc)
[187(1069)/576 at 11m57s] samba3.raw.samba3hide(nt4_dc)
[188(1070)/576 at 11m57s] samba3.raw.samba3badpath(nt4_dc)
[189(1071)/576 at 11m58s] samba3.raw.sfileinfo.rename(nt4_dc)
[190(1072)/576 at 11m58s] samba3.raw.session plain(nt4_dc)
[191(1074)/576 at 11m58s] samba3.raw.session enc(nt4_dc)
[192(1076)/576 at 11m58s] samba3.raw.samba3caseinsensitive(nt4_dc)
[193(1077)/576 at 11m59s] samba3.raw.samba3posixtimedlock(nt4_dc)
[194(1078)/576 at 12m4s] samba3.raw.samba3rootdirfid(nt4_dc)
[195(1079)/576 at 12m4s] samba3.raw.sfileinfo.end-of-file(nt4_dc)
[196(1080)/576 at 12m5s] samba3.raw.samba3checkfsp(nt4_dc)
[197(1081)/576 at 12m5s] samba3.raw.samba3closeerr(nt4_dc)
[198(1082)/576 at 12m5s] samba3.raw.samba3oplocklogoff(nt4_dc)
[199(1083)/576 at 12m5s] samba3.raw.samba3badnameblob(nt4_dc)
[200(1084)/576 at 12m6s] samba3.smb2.getinfo(nt4_dc)
[201(1090)/576 at 12m6s] samba3.smb2.lock aio(nt4_dc)
[202(1111)/576 at 12m9s] samba3.smb2.lock(nt4_dc)
[203(1132)/576 at 12m12s]
[204(1136)/576 at 12m12s] samba3.smb2.aio_delay(nt4_dc)
[205(1137)/576 at 12m16s] samba3.smb2.create(nt4_dc)
[206(1150)/576 at 12m18s] samba3.smb2.acls(nt4_dc)
[207(1158)/576 at 12m20s] samba3.smb2.notify(nt4_dc)
Testing notify cancel
Testing notify mkdir
Testing notify rmdir
Testing notify mkdir - rmdir - mkdir - rmdir
Testing buffered notify on create of 10 files
Testing notify on unlink for the first file
UNEXPECTED(failure): samba3.smb2.notify.dir(nt4_dc)
REASON: Exception: Exception: (../source4/torture/smb2/notify.c:398) wrong value for notify.smb2.out.num_changes  0x9 should be 0xa

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

A summary with detailed information can be found in:
TOP 10 slowest tests
samba3.raw.notify(nt4_dc) -> 103 -> 46
samba3.raw.oplock(nt4_dc) -> 45 -> 44
samba3.base.dir2(nt4_dc) -> 41
samba3.raw.lock(nt4_dc) -> 33
samba3.smbtorture_s3.crypt_client.OPLOCK1(nt4_dc) -> 30 -> 29
samba3.base.lock(nt4_dc) -> 17 -> 17
ERROR: test failed with exit code 1

More information about the samba-cvs mailing list