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-04-29-1843/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2011-04-29-1843/samba3.stderr http://git.samba.org/autobuild.flakey/2011-04-29-1843/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2011-04-29-1843/samba4.stderr http://git.samba.org/autobuild.flakey/2011-04-29-1843/samba4.stdout The top commit at the time of the failure was: commit df099e66240c7670c9f7b7dcccb1c38216bac3ec Author: Volker Lendecke <v...@samba.org> Date: Fri Apr 29 13:00:14 2011 +0200 s3: Avoid a potential 100% CPU loop in winbindd In the clustering case if ctdb is unhappy, winbindd_reinit_after_fork fails. This can lead to an endless loop depending on the scheduling of the parent vs child. Parent forks, child is immediately scheduled and exits. Parent gets SIGCHLD, parent is then scheduled before it sends the request out to the child. Parent tries to fork again immediately. The code before this patch did not really take into account that reinit_after_fork can fail. The code now sends the result of winbindd_reinit_after_fork to the parent and the parent only considers the child alive when it got NT_STATUS_OK. This was seen in 3.4 winbind. winbind has changed significantly since then, so it might be possible that this does not happen anymore in exactly this way. But passing up the status of reinit_after_fork and only consider the child alive when that's ok is the correct thing to do anyway. Autobuild-User: Volker Lendecke <vlen...@samba.org> Autobuild-Date: Fri Apr 29 17:58:19 CEST 2011 on sn-devel-104
