Re: autobuild: intermittent test failure detected

2014-08-05 Thread Stefan (metze) Metzmacher
Am 05.08.2014 um 09:36 schrieb autobuild: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/flakey.log The samba build logs are

Re: autobuild: intermittent test failure detected

2014-08-05 Thread Stefan (metze) Metzmacher
Am 05.08.2014 um 22:06 schrieb Stefan (metze) Metzmacher: Am 05.08.2014 um 09:36 schrieb autobuild: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here:

Re: autobuild: intermittent test failure detected

2014-08-05 Thread Stefan (metze) Metzmacher
Am 05.08.2014 um 22:08 schrieb Stefan (metze) Metzmacher: Am 05.08.2014 um 22:06 schrieb Stefan (metze) Metzmacher: Am 05.08.2014 um 09:36 schrieb autobuild: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is

Re: autobuild: intermittent test failure detected

2014-08-05 Thread Jeremy Allison
On Tue, Aug 05, 2014 at 10:14:45PM +0200, Stefan (metze) Metzmacher wrote: Am 05.08.2014 um 22:08 schrieb Stefan (metze) Metzmacher: Am 05.08.2014 um 22:06 schrieb Stefan (metze) Metzmacher: Am 05.08.2014 um 09:36 schrieb autobuild: The autobuild test system has detected an intermittent

Re: Flakey tests Re: autobuild: intermittent test failure detected

2014-01-04 Thread Stefan (metze) Metzmacher
Am 03.01.2014 17:10, schrieb Stefan (metze) Metzmacher: Am 23.12.2013 19:42, schrieb autobuild: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here:

Flakey tests Re: autobuild: intermittent test failure detected

2014-01-03 Thread Stefan (metze) Metzmacher
Am 23.12.2013 19:42, schrieb autobuild: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2013-12-23-1942/flakey.log The samba3 build logs are

Re: autobuild: intermittent test failure detected

2011-08-12 Thread Stefan (metze) Metzmacher
Hi Tridge, The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2011-08-12-1305/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-08-12-1305/samba3.stderr

Re: autobuild: intermittent test failure detected

2011-08-12 Thread tridge
Hi Metze, s4-test: use standard process model for 'dc' server this provides us with both 'standard' and 'single' process models in selftest, ensuring that we test the standard process model in the build farm Pair-Programmed-With: Andrew Bartlett

Re: autobuild: intermittent test failure detected

2011-08-09 Thread Stefan (metze) Metzmacher
Hi Andrew, The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2011-08-09-1406/flakey.log The samba3 build logs are available here:

Re: autobuild: intermittent test failure detected

2011-06-16 Thread Stefan (metze) Metzmacher
Hi, I think I've fixed the problems with this flakey test: samba3.posix_s3.winbind.wbclient .wbcListUsers See https://bugzilla.samba.org/show_bug.cgi?id=8215 for more details. metze The autobuild test system has detected an intermittent failing test in the current master tree. The

Re: autobuild: intermittent test failure detected

2011-04-29 Thread Stefan (metze) Metzmacher
Hi Tridge, http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stderr http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stdout Any idea why UNEXPECTED(error): samba4.nbt.winsreplication.owned is an error know instead of a failure, which would be ignored, because

Re: autobuild: intermittent test failure detected

2011-04-29 Thread Jelmer Vernooij
On Fri, 2011-04-29 at 21:29 +0200, Stefan (metze) Metzmacher wrote: Hi Tridge, http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stderr http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stdout Any idea why UNEXPECTED(error): samba4.nbt.winsreplication.owned

Re: autobuild: intermittent test failure detected

2011-04-29 Thread Stefan (metze) Metzmacher
Am 29.04.2011 21:57, schrieb Jelmer Vernooij: On Fri, 2011-04-29 at 21:29 +0200, Stefan (metze) Metzmacher wrote: Hi Tridge, http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stderr http://git.samba.org/autobuild.flakey/2011-04-28-0842/samba4.stdout Any idea why

Re: autobuild: intermittent test failure detected

2011-03-22 Thread Stefan (metze) Metzmacher
Hi, commit 4928d66fc2f469b75090c34f8d233026485e4a1e Author: Stefan Metzmacher me...@samba.org Date: Mon Mar 21 11:21:57 2011 +0100 libcli/security: make sure that we don't grant SEC_STD_DELETE to the owner by default In the file server SEC_STD_DELETE is granted on the

Re: autobuild: intermittent test failure detected

2011-02-14 Thread Matthieu Patou
Hello, I suspect that the system suspect the changeset pointed in the message (most probably the last change) to cause intermittent errors. The error is there: 430/702 in 17m40s] samba4.base.defer_open(dc) Using seed 1297660749 dos charset 'CP850' unavailable - using ASCII dos charset

Re: autobuild: intermittent test failure detected

2010-12-11 Thread Stefan (metze) Metzmacher
Am 11.12.2010 06:44, schrieb Andrew Tridgell: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2010-12-11-0644/flakey.log The source3 build logs

Re: autobuild: intermittent test failure detected

2010-12-11 Thread Jelmer Vernooij
On Sat, 2010-12-11 at 11:08 +0100, Stefan (metze) Metzmacher wrote: Am 11.12.2010 06:44, schrieb Andrew Tridgell: The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: