autobuild: intermittent test failure detected

autobuild autobuild at
Mon Sep 15 04:43:15 MDT 2014

The autobuild test system has detected an intermittent failing test in 
the current master tree.

The autobuild log of the failure is available here:

The samba build logs are available here:
The top commit at the time of the failure was:

commit 7bc2e2d0d4a6706769a436798aa29d18a8f7c221
Author: Volker Lendecke <vl at>
Date:   Wed Sep 10 16:13:18 2014 +0200

    messaging_dgm: Don't expose the messaging_dgm_context
    Right now we can only support one messaging_dgm_context per process
    anyway, the code has checks for this. I would like to keep it that
    way, in the future we will have multiple messaging_context's or
    imessaging_context's filtering based upon the dst server_id.
    Why this change? messaging_dgm's lockfile contains the
    serverid->unique_id. When designing messaging_dgm, I had in mind to
    remove the serverid.tdb and replace it with the dgm lockfiles for server
    lookup and enumeration. I have a WIP-patchset that gets rid of almost
    all users of serverid.tdb. The problem is serverid_exists. Here we don't
    have a messaging_context available, and it would be pretty intrusive
    to make it so. This problem has plagued us since ctdb was developed,
    see for example the comment
     * This is a Samba3 hack/optimization. Routines like process_exists need to
     * talk to ctdbd, and they don't get handed a messaging context.
    in messaging_ctdb.c. This patchset removes this problem in a radical way:
    Treat the messaging_dgm context as one globally available structure and
    be done with it. The ctdb socket could go the same way in the future.
    Signed-off-by: Volker Lendecke <vl at>
    Reviewed-by: Stefan Metzmacher <metze at>
    Autobuild-User(master): Stefan Metzmacher <metze at>
    Autobuild-Date(master): Sun Sep 14 16:29:30 CEST 2014 on sn-devel-104

More information about the samba-cvs mailing list