[Buildbot-devel] Detect termination of shellcommand due to timeout

[Marco]

Thanks, that's the same thing I had tried too. However I see that the
compressed logs stored on the master for the step do include those
lines ("command timed out: ... attempting to kill
process killed by signal 9, program finished with exit code -1 etc.)
so I guess there should be a way to access that information?


2011/10/15 Dan Kegel <dank at kegel.com>:
> On Sat, Oct 15, 2011 at 3:56 AM, Marco <listaddr at gmail.com> wrote:
>> Hello, when a shell command step fails, is it possible to detect
>> whether it was killed due to lack of output timeout (ie, 1200 seconds
>> by default)?
>>
>> Reading through the documentation I haven't found a way to detect
>> this, which I guess should be a fairly common need.
>
> I ran into this, too, kind of.
> In my messageFormatter, I look at the text form of test logs,
> and annoyingly, the 'killed, timeout' message from buildbot
> isn't in those logs, it's only in the html logs.
> But the question is moot for me, as I now do finer
> grained timeouts outside of buildbot.
> - Dan
>