[Buildbot-devel] question about timeout between master and slave

[Stefan Schlauch]

Hi Mark,

thank you.

To make an output like "hello world", in our case ".", we solved the timeout issue. I was increasing the ShellCommand timeout up to 30 minutes but had the same problem. To generate outputs we can thinking about to decrease the timeout to optimize the buildsteps. But first I need the new server farm for the buildbot systems :)


Von: Mark Berger [mailto:mark.berger.j at gmail.com]
Gesendet: Dienstag, 17. September 2013 15:46
An: Stefan Schlauch
Cc: Buildbot Devel
Betreff: Re: [Buildbot-devel] question about timeout between master and slave

Hi Stefan,

If there is no output for more than 20 minutes, by default the process will be killed so I believe that is your problem. You could solve it by printing 'hello world' every 5 or 10 minutes or you could increase the ShellCommand's timeout parameter to something larger than 1200 seconds. You could also disable timeout by supplying None.

Here is the documentation on the ShellCommand. If you scroll down a bit, there is documentation on the timeout parameter: http://docs.buildbot.net/latest/manual/cfg-buildsteps.html#shellcommand

I hope this helps!

- Mark Berger

On Tue, Sep 17, 2013 at 6:08 AM, Stefan Schlauch <stefan.schlauch at hella-gutmann.com<mailto:stefan.schlauch at hella-gutmann.com>> wrote:
Hello,

I have a question about the timeout function between master and slave. If i understand the documentation right, the standard-timeout is 20 minutes and the master will kill the step when the slave isn't answering within this time?
Since nearly two weeks I have a problem with a buildstep I can't really solve. There is a step which is executing many exe-files (selfmade from the coder-team) for doing different tasks and build data for the software. There was an update for one "data-builder" (exe-file) and since this time the step is always getting a timeout.
If I execute the "data-builder" on the command shell of the buildslave, I can see that some outputs take a very long time (some more then 20 minutes). Is this reason why the master is getting a timeout? Is the master "listening" on the standard output? Can we solve this timeout problem if we build in a "hello world" every 5 or 10 minutes, so the command shell is throwing out an output?

Thanks and regards

Stefan Schlauch


--
Hella Gutmann Solutions GmbH * Unternehmensform: Gesellschaft mit beschraenkter Haftung *
Firmensitz: 79241 Ihringen * Eingetragen im Handelsregister: AG Freiburg i.Br., HRB 290194 *
Geschaeftsfuehrer: Kurt Gutmann, Patrick Lux, Bjoern Rietschel * USt-IdNr.: DE142208666


------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net<mailto:Buildbot-devel at lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/buildbot-devel


________________________________
--
Hella Gutmann Solutions GmbH * Unternehmensform: Gesellschaft mit beschraenkter Haftung *
Firmensitz: 79241 Ihringen * Eingetragen im Handelsregister: AG Freiburg i.Br., HRB 290194 *
Geschaeftsfuehrer: Kurt Gutmann, Patrick Lux, Bjoern Rietschel * USt-IdNr.: DE142208666
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130919/2016b31a/attachment.html>