Re: autobuild: intermittent test failure detected
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 available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/samba.stderr I fear the recent glibc security update causes segfaults... I'll have a look at it tomorrow. metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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: http://git.samba.org/autobuild.flakey/2014-08-05-0936/flakey.log The samba build logs are available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/samba.stderr I fear the recent glibc security update causes segfaults... I'll have a look at it tomorrow. I just found https://bugs.launchpad.net/ubuntu/+bug/1352769 metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/flakey.log The samba build logs are available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/samba.stderr I fear the recent glibc security update causes segfaults... I'll have a look at it tomorrow. I just found https://bugs.launchpad.net/ubuntu/+bug/1352769 I did the following on sn and sn-devel-104 root@sn:~# /etc/init.d/nscd stop root@sn:~# update-rc.d -f nscd remove metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 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 available here: http://git.samba.org/autobuild.flakey/2014-08-05-0936/samba.stderr I fear the recent glibc security update causes segfaults... I'll have a look at it tomorrow. I just found https://bugs.launchpad.net/ubuntu/+bug/1352769 I did the following on sn and sn-devel-104 root@sn:~# /etc/init.d/nscd stop root@sn:~# update-rc.d -f nscd remove Thanks Metze, I'll retry the autobuild.
Re: Flakey tests Re: autobuild: intermittent test failure detected
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: http://git.samba.org/autobuild.flakey/2013-12-23-1942/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba3.stderr http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba.stderr http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba.stdout The top commit at the time of the failure was: commit 819e1f561df5074ae21db77c6558b34f4b0e1351 Author: Garming Sam garm...@catalyst.net.nz Date: Mon Dec 23 17:12:39 2013 +1300 selftest: add rodc and other env tests for wbinfo This introduced some problems with flakey builds, please find a workaround attached. I'm currently doing manual autobuild with this, lets see if it gets better while build over the weekend. Just 1 failed autobuild (with this patch) and about 13 (without it), it would be nice if someone could give me a review+ and push it master. metze
Flakey tests Re: autobuild: intermittent test failure detected
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 available here: http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba3.stderr http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba.stderr http://git.samba.org/autobuild.flakey/2013-12-23-1942/samba.stdout The top commit at the time of the failure was: commit 819e1f561df5074ae21db77c6558b34f4b0e1351 Author: Garming Sam garm...@catalyst.net.nz Date: Mon Dec 23 17:12:39 2013 +1300 selftest: add rodc and other env tests for wbinfo This introduced some problems with flakey builds, please find a workaround attached. I'm currently doing manual autobuild with this, lets see if it gets better while build over the weekend. metze
Re: autobuild: intermittent test failure detected
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 http://git.samba.org/autobuild.flakey/2011-08-12-1305/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-08-12-1305/samba4.stderr http://git.samba.org/autobuild.flakey/2011-08-12-1305/samba4.stdout The top commit at the time of the failure was: commit 6b3a12b0f4c38c87a1f1ff4227ab78ac7624289d Author: Andrew Tridgell tri...@samba.org Date: Fri Aug 12 14:37:04 2011 +1000 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 abart...@samba.org I fear this change made autobuild a bit more unstable I saw the following error a few times today: [1064/1145 in 1h2m11s] samba4.nbt.winsreplication(dc) Test if we always get back the same assoc_ctx Setup wrepl connections UNEXPECTED(failure): samba4.nbt.winsreplication.assoc_ctx2 REASON: _StringException: _StringException: ../source4/torture/nbt/winsreplication.c:200: status was NT_STATUS_HOST_UNREACHABLE, expected NT_STATUS_OK: Incorrect status I also noticed that samba4 make test needs over 1h 20 now. metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 abart...@samba.org I fear this change made autobuild a bit more unstable I saw the following error a few times today: The change really is quite important. We have previously only been testing S4 in single mode in the build farm, which doesn't represent how real users run it. A bug was introduced in tevent a while ago which broke standard mode, and we didn't even notice. If this has made some tests less stable then we need to fix those tests. Perhaps the timing is less predictable in standard mode. I also noticed that samba4 make test needs over 1h 20 now. It has needed well over an hour for a while now. The big jump was the change to run all the s3 tests in the top level build. Cheers, Tridge
Re: autobuild: intermittent test failure detected
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: http://git.samba.org/autobuild.flakey/2011-08-09-1406/samba3.stderr http://git.samba.org/autobuild.flakey/2011-08-09-1406/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-08-09-1406/samba4.stderr http://git.samba.org/autobuild.flakey/2011-08-09-1406/samba4.stdout Do you have an idea why the samba3.blackbox.smbclient_auth.plain tests are flakey? I tried make test TESTS=secshare SMBD_VALGRIND=valgrind --num-callers=30 --log-file=smbd.vg.log --trace-children=yes, but didn't find anything. UNEXPECTED(error): creating directory /memdisk/autobuild/flakey/b28206/samba4/bin/ab/secserver/ncalrpc: File exists is very strange and I can't find the related code using git grep 'creating directory' metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2011-06-16-0225/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-06-16-0225/samba3.stderr http://git.samba.org/autobuild.flakey/2011-06-16-0225/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-06-16-0225/samba4.stderr http://git.samba.org/autobuild.flakey/2011-06-16-0225/samba4.stdout signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 it's marked in knownfail? To me it seems that the knownfail feature doesn't work anymore. metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 is an error know instead of a failure, which would be ignored, because it's marked in knownfail? To me it seems that the knownfail feature doesn't work anymore. knownfail only works for failures (i.e. we check for a particular error but a different one was returned), not for errors (e.g. segfaults). This is intentional; an error is often a sign of a broken testsuite. Cheers, Jelmer signature.asc Description: This is a digitally signed message part
Re: autobuild: intermittent test failure detected
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 UNEXPECTED(error): samba4.nbt.winsreplication.owned is an error know instead of a failure, which would be ignored, because it's marked in knownfail? To me it seems that the knownfail feature doesn't work anymore. knownfail only works for failures (i.e. we check for a particular error but a different one was returned), not for errors (e.g. segfaults). This is intentional; an error is often a sign of a broken testsuite. I know, but that test used to generate a failure and not an error before. So something seemed to be changed, because it started to be flakey again arround commit 1c5cc4a2d1449296a96e8a137dc177191df00c8d. I'll change _NBT_ASSERT() and _NBT_ASSERT_STRING() to use the torture_assert macros, so that's a failure again, but we need to bisect why it is failing there now, while it didn't fail before with an error. metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 file/directory or by FILE_DELETE_CHILD on the parent directory. metze I've pushed a fix for this to autobuild... metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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 'CP850' unavailable - using ASCII dos charset 'CP850' unavailable - using ASCII dos charset 'CP850' unavailable - using ASCII Child 3 failed to start! Child 2 failed to start! Child 1 failed to start! Child 0 failed to start! Starting 4 clients 4 clients started UNEXPECTED(error): samba4.base.defer_open.defer_open REASON: _StringException: _StringException: Unknown error/failure FAILED (0 failures and 1 errors in 0 testsuites) A summary with detailed information can be found in: ./st/summary test: running (/usr/bin/perl /memdisk/tridge/flakey/b10604/samba4/selftest/selftest.pl --prefix=./st --builddir=. --srcdir=/memdisk/tridge/flakey/b10604/samba4 --exclude=/memdisk/tridge/flakey/b10604/samba4/source4/selftest/skip --testlist=/usr/bin/python /memdisk/tridge/flakey/b10604/samba4/source4/selftest/tests.py| --exclude=/memdisk/tridge/flakey/b10604/samba4/source4/selftest/slow --socket-wrapper touch ./st/st_done) | /usr/bin/python -u /memdisk/tridge/flakey/b10604/samba4/selftest/filter-subunit --expected-failures=/memdisk/tridge/flakey/b10604/samba4/source4/selftest/knownfail --fail-immediately | tee ./st/subunit | /usr/bin/python -u /memdisk/tridge/flakey/b10604/samba4/selftest/format-subunit --prefix=./st --immediate ERROR: test failed with exit code 1 It's clearly not the pb of the patch but it would be good to know why and if this tests is time to times failing. Matthieu On 14/02/2011 08:19, Andrew Tridgell wrote: 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-02-14-0619/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-02-14-0619/samba3.stderr http://git.samba.org/autobuild.flakey/2011-02-14-0619/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-02-14-0619/samba4.stderr http://git.samba.org/autobuild.flakey/2011-02-14-0619/samba4.stdout The top commit at the time of the failure was: commit b2e126cddc8a9f95426fa802b6d66c88629721b3 Author: Matthieu Patoum...@matws.net Date: Sun Jan 9 15:55:24 2011 +0300 s4:selftest: add tests with seal and sign for backupkey We need to specify sign and seal as the protocol operate really only on sealed protected connections, in other case we are just checking that the server returns something like unwilling to perform due to weak security. Signed-off-by: Stefan Metzmacherme...@samba.org Signed-off-by: Andrew Bartlettabart...@samba.org Autobuild-User: Andrew Bartlettabart...@samba.org Autobuild-Date: Mon Feb 14 01:48:39 CET 2011 on sn-devel-104 -- Matthieu Patou Samba Teamhttp://samba.org Private repo http://git.samba.org/?p=mat/samba.git;a=summary
Re: autobuild: intermittent test failure detected
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 are available here: http://git.samba.org/autobuild.flakey/2010-12-11-0644/source3.stderr http://git.samba.org/autobuild.flakey/2010-12-11-0644/source3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2010-12-11-0644/source4.stderr http://git.samba.org/autobuild.flakey/2010-12-11-0644/source4.stdout The top commit at the time of the failure was: commit 35fbc7bbda5851f7172538f79fc79be201f1d521 Author: Jelmer Vernooij jel...@samba.org Date: Sat Dec 11 03:26:31 2010 +0100 s4-smbtorture: Make test names lowercase and dot-separated. This is consistent with the test names used by selftest, should make the names less confusing and easier to integrate with other tools. Autobuild-User: Jelmer Vernooij jel...@samba.org Autobuild-Date: Sat Dec 11 04:16:13 CET 2010 on sn-devel-104 I wonder how this passed autobuild, as the ECHO-UDP test can never be found... I'm pushing fixes for it to autobuild now. metze metze signature.asc Description: OpenPGP digital signature
Re: autobuild: intermittent test failure detected
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: http://git.samba.org/autobuild.flakey/2010-12-11-0644/flakey.log The source3 build logs are available here: http://git.samba.org/autobuild.flakey/2010-12-11-0644/source3.stderr http://git.samba.org/autobuild.flakey/2010-12-11-0644/source3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2010-12-11-0644/source4.stderr http://git.samba.org/autobuild.flakey/2010-12-11-0644/source4.stdout The top commit at the time of the failure was: commit 35fbc7bbda5851f7172538f79fc79be201f1d521 Author: Jelmer Vernooij jel...@samba.org Date: Sat Dec 11 03:26:31 2010 +0100 s4-smbtorture: Make test names lowercase and dot-separated. This is consistent with the test names used by selftest, should make the names less confusing and easier to integrate with other tools. Autobuild-User: Jelmer Vernooij jel...@samba.org Autobuild-Date: Sat Dec 11 04:16:13 CET 2010 on sn-devel-104 I wonder how this passed autobuild, as the ECHO-UDP test can never be found... The tests passed locally for me, but I hadn't rebased after Kai pushed the ECHO-UDP test. So I wonder if there's something wrong in the rebase logic in autobuild? Cheers, Jelmer signature.asc Description: This is a digitally signed message part
