[SCM] Samba Shared Repository - branch master updated

Noel Power npower at samba.org
Sat Apr 4 01:13:02 UTC 2020

The branch, master has been updated
       via  8cad448ab24 selftest/flapping: mark samba3.nbt.dgram.netlogon.* as flapping
      from  78e1492f218 smbd: move files_struct.lock_failure_seen to a bitfield


- Log -----------------------------------------------------------------
commit 8cad448ab24bb0290c52405ea5d1ae22a759f587
Author: Noel Power <noel.power at suse.com>
Date:   Fri Apr 3 16:05:37 2020 +0100

    selftest/flapping: mark samba3.nbt.dgram.netlogon.* as flapping
    Post SMB1/SMB2 test env split to help in removing smb1
    samba3.nbt.dgram.netlogon* fails randomly. It is unrelated as far
    as we can see to the changes but must be a side affect of runtime
    order or some such.
    Signed-off-by: Noel Power <noel.power at suse.com>
    Reviewed-by: Ralph Boehme <slow at samba.org>
    Autobuild-User(master): Noel Power <npower at samba.org>
    Autobuild-Date(master): Sat Apr  4 01:12:05 UTC 2020 on sn-devel-184


Summary of changes:
 selftest/flapping.d/nbt_dgram | 7 +++++++
 1 file changed, 7 insertions(+)
 create mode 100644 selftest/flapping.d/nbt_dgram

Changeset truncated at 500 lines:

diff --git a/selftest/flapping.d/nbt_dgram b/selftest/flapping.d/nbt_dgram
new file mode 100644
index 00000000000..b4e4c3b4ac8
--- /dev/null
+++ b/selftest/flapping.d/nbt_dgram
@@ -0,0 +1,7 @@
+# following SMB1/SMB2 test env split it seems this test
+# fails randomly however it doesn't seem to be directly
+# related to the changes (e.g. not protocl negotiation
+# specific) Best guess is the order of test having being
+# changed (as a result of test moving env) or some other
+# strange env related side affect is causing this.

Samba Shared Repository

More information about the samba-cvs mailing list