autobuild failure for task source4 during test

Volker Lendecke Volker.Lendecke at SerNet.DE
Tue Nov 30 09:46:38 MST 2010

On Tue, Nov 30, 2010 at 05:37:19PM +0100, Stefan (metze) Metzmacher wrote:
> > On Tue, Nov 30, 2010 at 05:25:18PM +0100, Kai Blin wrote:
> >> Same here.
> >>
> >> My commit is a rewording of a section of the smb.conf manpage (see
> >> 8268e030235b6cb5e6288a53133bba1faa9e63b1 for the equivalent fix in 3.6)
> >>
> >> I don't think this should be causing an error of
> >> ERROR: Testsuite[samba4.drs.delete_object.python(vampire_dc)]
> >> REASON: unable to set up environment vampire_dc - exiting
> >>
> >> So, what's the way to proceed here? Volker's autobuild failed on the
> >> same test with a different error, so that test is clearly broken. Would
> >> a patch to disable the failing test be acceptable in a case like this?
> > 
> > The Samba4 developers should step in here with a comment.
> I think the failing tests should be added to knownfail or skip
> (Together with a mail to samba-technical, that someone should fix them),
> if they prevent such trivial patches from going through.

Alternatively, someone could add magic to skip the source3
tests if only source4 was touched by a checkin, and to skip
the source4 test if only source3 was touched by a checkin.
Neither of these cases should affect the respective opposite


More information about the samba-technical mailing list