[Buildbot-devel] Slave doesnt create output directory

Nick Trout nick at rockstarvancouver.com
Tue May 3 04:43:40 UTC 2005


I could try and track this down but I figure this will be very quick for
you to fix Brian... ;o)

When I start up a simple build factory using ShellCommand:

<<<<
# Create basic BuildFactory object to generate our steps for us
f1 = factory.BuildFactory()

# Tell the BuildFactory about the steps
f1.steps.append(s(step.ShellCommand, command="dir" ))
>>>>

it kacks because the "build" directory hasn't been created:

<<<<
command 'dir' in dir Z:\Temp\slave2\mytest2\build (timeout 1200 secs)

remoteFailed: [Failure instance: Traceback from remote host -- Traceback
(most recent call last):
Failure: buildbot.slave.commands.AbandonChain: -1
>>>>

I.e. my slave .tap is in Z:\Temp\slave2 with the work dir as mytest2 but
no "build" directory is created. This causes output to fail with the
above message. This could be another Windows difference. If I create the
"build" directory everything works fine for the ShellCommand step.

Oh, also the buildbot slave command doesn't work. I have to use mktap.
It seems to foul up the arguments and miss the password for some reason.

Nick





More information about the devel mailing list