[Buildbot-devel] Increase Timeout value for master

Wang, Yu yu.wang at intel.com
Fri Feb 8 22:25:18 UTC 2008


The timeout feature finally works for me.  Now I have added
sys.stdout.flush() in python script to force the stdout to be sent
over to the master.  But it has been inconsistent as when it does 
flush and when it doesn't.

Any suggestions?
Thanks,
Jean

-----Original Message-----
From: Shaun McDonald [mailto:shaun at shaunmcdonald.me.uk] 
Sent: Friday, February 08, 2008 11:50 AM
To: Wang, Yu
Cc: Charles Lepple; buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] Increase Timeout value for master


On 7 Feb 2008, at 22:15, Wang, Yu wrote:

> You are right, the default is 20mins.  Now I have added "timeout=3600"
> in the f.addStep(ShallCommand, ...), but the status stdio page still
> shows the timeout as 1200 secs.  Is the timeout feature broken in  
> 0.7.5?
>

The custom timeout works for our config file on a master running 0.7.5.
http://ootermite.googlecode.com/svn/trunk/buildbot/buildmaster/master.cf
g

I'm assuming you've restarted both the master and the slave in a clean  
shell if a reconfig on the master isn't doing the trick as it should be.

When you run the script locally how long does it take? Try running the  
command with the command time before it, so that it computes the  
duration of the task for you.

Our cws_get step doesn't stream the output live, though all other  
scripts do stream it live. I've not yet worked out why.
http://ootermite.googlecode.com/svn/trunk/buildbot/buildslave/scripts/

Shaun

> Thanks,
> Jean
>
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Wednesday, February 06, 2008 5:50 PM
> To: Wang, Yu
> Cc: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] Increase Timeout value for master
>
> On Feb 6, 2008 5:36 PM, Wang, Yu <yu.wang at intel.com> wrote:
>> I am running buildbot 0.7.5 and I need the timeout value longer than
> 12 mins
>> (current default) for master to wait for slave to respond with an  
>> exit
>> status.  Currently when it exceed 12 mins, the master considers the
> step as
>> failing.
>
> If the timeout is really 12 minutes, then check your master.cfg to see
> if the timeout parameter is being set on the buildstep (I was under
> the impression that the default timeout was 1200 seconds, or 20
> minutes.)
>
> 'timeout' is a parameter to all buildsteps which subclass ShellCommand
> (and possibly other steps).
>
> http://buildbot.sourceforge.net/manual-0.7.5.html#ShellCommand
>
> -- 
> - Charles Lepple
>
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel





More information about the devel mailing list