[Buildbot-devel] ShellCommand timeout when command fails (win32)

Brian Warner warner-buildbot at lothar.com
Fri Feb 25 06:36:41 UTC 2005

> I have the following build step in BuildFactory:
> s(step.Test, command=["check.bat"])
> However, in my situation, the file check.bat is not found, and the slave
> correctly complains about that (see below). The problem is that the
> buildmaster doesn't take notice of this, but waits for the timeout.
> I would expect it would report failure immediately. Is there any
> reason why it should wait in the timeout when the command clearly
> fails?

Hrm. You're right. It looks like the slave noticed the problem (the exception
was caught by bot.SlaveBuilder.commandComplete) and sent back an error
message, but something is broken with that error-reporting mechanism, as it
didn't cause the step to be flunked.

What was the buildmaster-side log for this same event?


More information about the devel mailing list