[Buildbot-devel] Forcing buildbot to execute the next buildstep if no return code was received for the previous step

[David Mor]

Dear Buildbot Developers,

  I'm currently trying to automate ETL log captures by trying to start traceview via Shellcommand before tests are run.
However, since traceview doesn't seem to issue a return coded until a key is manually pressed in the traceview popup window after it is instantiated in  command prompt and , buildbot will wait and kill the process after 1200 seconds (default value).
Is there any way to tell buildbot that it is okay to proceed onto the next build step (start the tests) without waiting for a return code and allow the process to live even
after timeout?
is there any other way around this?

The logfiles attribute in  Shellcommands don't seem to be able to substitute traceview in this circumstance.

Thank you for your support.

Sincerely,
  David Mor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20100709/dcb8422a/attachment.html>