[Buildbot-devel] Testing a client-server system
Axel Hecht
l10n.moz at googlemail.com
Sun Mar 8 23:43:14 UTC 2009
2009/3/9 Brad Hards <bradh at frogmouth.net>
> On Monday 09 March 2009 12:54:14 am Axel Hecht wrote:
> > Create a step that starts up the server, and waits for the server to be
> > actually ready.
> OK, this is the part I need some help with. I take it you are suggesting I
> add
> a custom build step that runs the server, and returns "complete" before the
> server actually exits.
>
> I'm not sure how to do that.
>
> Ideally I'd like to keep capturing stdout from the server.
>
> > within the same build, add a step to run your test.
> No problem with this part (since I can just run the various tests and
> killall
> step at the end). I just need a hint on that first part...
>
> Thanks for the advice.
>
I don't have a remote clue. I'm pretty sure that one can start up samba as a
daemon and get log files. Starting samba and keeping it running while
watching stdout could be possible, but you'd have to fake the end of the
process. That would probably require you to hack a buildbot slave command.
Daemon and log parsing sounds more straightforward. As straightforward as a
"sudo" on a slave could be. If I knew samba even remotely, I'd give you an
educated statement on how scary I think that is. ;-)
Axel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090309/e6f8d994/attachment.html>
More information about the devel
mailing list