Subject: Re: Defunct processes in buildslave after ShellCommand completion - msg#00033
List: python.buildbot.devel
Hi there
I've just seen this problem as well. I wonder if there might be a fix
that doesn't involve upgrading Python?
I'm thinking it could be a problem with the 'popen' routines in Python,
which were improved a lot with the release of 2.4.
Cheers
JP
On Thu, 16 Nov 2006 09:12:35 -0500, "Mitch Oliver"
<mitch.oliver-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> said:
>
I wanted to reply to this as I found a solution. Upgrading to Python
>
2.5 has resolved the issue. It appears that the issue itself is in
>
Twisted and not buildbot.
>
>
On 11/10/06, Mitch Oliver
>
<mitch.oliver-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
>
> After a ShellCommand completes I frequently end up with defunct
>
> processes in my process list, and the commands always end up with the
>
> following exception in my buildmaster waterfall:
>
> command timed out: 1200 seconds without output, killing pid [pid]
>
> SIGKILL failed to kill process
>
> using fake rc=-1
>
> program finished with exit code -1
>
>
>
> remoteFailed: [Failure instance: Traceback from remote host --
>
> Traceback (most recent call last):
>
> Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill
>
> process
>
> ]
>
>
>
> This occurs using buildbot 0.7.4 in Python 2.3.3 with Twisted 2.4.0 on
>
> Solaris 10 (Sparc).
>
>
>
> Has anyone else run into this problem? I saw a message in the
>
> archives about something similar on NetBSD, but the thread seems to
>
> have died.
>
>
>
> Thanks,
>
> Mitch Oliver
>
>
>
>
-------------------------------------------------------------------------
>
Take Surveys. Earn Cash. Influence the Future of IT
>
Join SourceForge.net's Techsay panel and you'll get the chance to share
>
your
>
opinions on IT & business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
_______________________________________________
>
Buildbot-devel mailing list
>
Buildbot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
>
https://lists.sourceforge.net/lists/listinfo/buildbot-devel
--
John Pye
john-9Y9lekcF0YBbcPXmkBQw5dBPR1lH4CV8@xxxxxxxxxxxxxxxx
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Problem running SVNPoller under 0.7.5
Hi
It seems that the SVNPoller does not handle correctly some failures when
trying to get a log from SVN.
Here some lines from my twisted.log
> 2006/12/21 11:33 CET [-] SVNPoller finished polling
> 2006/12/21 11:33 CET [-] _finished : [Failure instance: Traceback (failure
> with no frames): exceptions.IOError: got stderr: "svn: PROPFIND request
> failed on '/svn/xenomai/trunk'\n" ]
> 2006/12/21 11:33 CET [-] Unhandled error in Deferred:
> 2006/12/21 11:33 CET [-] Traceback (most recent call last):
> Failure: exceptions.IOError: got stderr: "svn: PROPFIND request
> failed on '/svn/xenomai/trunk'\n"
>
> 2006/12/21 11:57 CET [HTTPChannel,5,84.73.191.27] 84.73.191.27 - -
> [21/Dec/2006:10:57:23 +0000] "GET / HTTP/1.1" 200 111660 "-" "Mozilla/4.0
> (compatible; MSIE 6.0; Windows 98)"
I had the same error earlier once on 2006/12/12 21:55 CET
Manually I have no problem doing a svn ls http://svn.gna.org/svn/xenomai/trunk
The buildbot can be seen at http://ngiger.dyndns.org/buildbot/.
Any ideas? Has anybody seen this error too?
Best regards
--
Niklaus Giger
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Next Message by Date:
click to view message preview
Re: Feature request: button on the waterfall to start a "waiting" build
Quoting Stephen Davis <buildbot-Q/NP9tXuLgjdtAWm4Da02A@xxxxxxxxxxxxxxxx>:
> That doesn't quite work for all scenarios b/c blame isn't recognized
> for forced builds. A button on the force build page that short-
> circuits the current timeout would be handy. I'd like it so I can
> make the build go ahead and run so I can go home a little sooner
> after my last checkin of the day. :-)
>
> stephen
>
That's exactly what I'd like: short-circuit the timeout. If I commit
then go to
the buildbot waterfall and click "force build", the buildbot will start a new
build while the one triggered by my commit will still remain scheduled
once the
timeout has elapsed.
--
SIGOURE Benoit aka Tsuna
_____
/EPITA\ Promo 2008, LRDE
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Previous Message by Thread:
click to view message preview
Problem running SVNPoller under 0.7.5
Hi
It seems that the SVNPoller does not handle correctly some failures when
trying to get a log from SVN.
Here some lines from my twisted.log
> 2006/12/21 11:33 CET [-] SVNPoller finished polling
> 2006/12/21 11:33 CET [-] _finished : [Failure instance: Traceback (failure
> with no frames): exceptions.IOError: got stderr: "svn: PROPFIND request
> failed on '/svn/xenomai/trunk'\n" ]
> 2006/12/21 11:33 CET [-] Unhandled error in Deferred:
> 2006/12/21 11:33 CET [-] Traceback (most recent call last):
> Failure: exceptions.IOError: got stderr: "svn: PROPFIND request
> failed on '/svn/xenomai/trunk'\n"
>
> 2006/12/21 11:57 CET [HTTPChannel,5,84.73.191.27] 84.73.191.27 - -
> [21/Dec/2006:10:57:23 +0000] "GET / HTTP/1.1" 200 111660 "-" "Mozilla/4.0
> (compatible; MSIE 6.0; Windows 98)"
I had the same error earlier once on 2006/12/12 21:55 CET
Manually I have no problem doing a svn ls http://svn.gna.org/svn/xenomai/trunk
The buildbot can be seen at http://ngiger.dyndns.org/buildbot/.
Any ideas? Has anybody seen this error too?
Best regards
--
Niklaus Giger
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
Next Message by Thread:
click to view message preview
Re: Defunct processes in buildslave after ShellCommand completion
A followup on this problem from a week ago:
I found that I needed to set usepty=0 in the buildbot.tac file for the
Solaris buildslave. This fixed my problem of commands timing out / not
returning an exit code.
Found here -- obviously not a new problem:
http://agiletesting.blogspot.com/2006/03/running-buildbot-on-various-platforms.html
Cheers
JP
John Pye wrote:
> Hi there
>
> I've just seen this problem as well. I wonder if there might be a fix
> that doesn't involve upgrading Python?
>
> I'm thinking it could be a problem with the 'popen' routines in Python,
> which were improved a lot with the release of 2.4.
>
> Cheers
> JP
>
> On Thu, 16 Nov 2006 09:12:35 -0500, "Mitch Oliver"
> <mitch.oliver-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> said:
>
>> I wanted to reply to this as I found a solution. Upgrading to Python
>> 2.5 has resolved the issue. It appears that the issue itself is in
>> Twisted and not buildbot.
>>
>> On 11/10/06, Mitch Oliver
>> <mitch.oliver-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
>>
>>> After a ShellCommand completes I frequently end up with defunct
>>> processes in my process list, and the commands always end up with the
>>> following exception in my buildmaster waterfall:
>>> command timed out: 1200 seconds without output, killing pid [pid]
>>> SIGKILL failed to kill process
>>> using fake rc=-1
>>> program finished with exit code -1
>>>
>>> remoteFailed: [Failure instance: Traceback from remote host --
>>> Traceback (most recent call last):
>>> Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill
>>> process
>>> ]
>>>
>>> This occurs using buildbot 0.7.4 in Python 2.3.3 with Twisted 2.4.0 on
>>> Solaris 10 (Sparc).
>>>
>>> Has anyone else run into this problem? I saw a message in the
>>> archives about something similar on NetBSD, but the thread seems to
>>> have died.
>>>
>>> Thanks,
>>> Mitch Oliver
>>>
>>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV