[PATCH] Cache messaging dgm connections

[Michael Adam]

On 2016-09-14 at 21:38 -0700, Jeremy Allison wrote:
> On Thu, Sep 15, 2016 at 04:27:03PM +1200, Garming Sam wrote:
> > The test is:
> > 
> > samba4.drs.replica_sync.python
> > 
> > But, I don't really have a good answer on how to reproduce the failure.
> > It's most likely produced by some dnsZone object in the database, but
> > triggering looks difficult as I've already run the dns notify module in
> > a test env by adding dns zones. Likewise running the test on its own
> > doesn't reproduce it.
> > 
> > While it seems unpleasant, the easiest way to check the fix is probably
> > convincing yourself that the fix is correct before attempting to see if
> > sn-devel-144 no longer faults (whether that's pushing it upstream and
> > waiting for more periodic flakey builds or a loop of private autobuilds).
> 
> I guess I don't understand what the "flakey build"
> process is doing differently from the regular build
> process.

Nothing. It just does autobuilds in a loop.
And reports any unexpected failures by mail.

By the nature of flakeyness, those flakey tests
fail on some (and not all) of those runs, and you
can not know in advance, when.

So in order to catch a flakey test, you'd identify
which test is affected and then run, e.g.
"make test TEST=samba4.drs.replica_sync"
in a loop until if fails.

Cheers - Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160918/51918b70/signature.sig>