[Buildbot-devel] Slave working as buildslave but failing as latentbuildslave

[Julia S.S.]

Another major difference is that as normal buildslave SHELL=/bin/bash while
as latent is /bin/sh
Also in latent following env vars are missing:

USER, LESSCLOSE, LESSOPEN, MAIL, SHLVL, SSH_CLIENT, SSH_CONNECTION,
SSH_TTY , TERM, USER (LOGNAME is present)

So problem seems that login somehow is different

I'm using Fabrizio's EC2LatentBuildSlaveInstanceID class but that only
seems to be in charge of starting and stopping the machine.



On Mon, Aug 26, 2013 at 8:51 AM, Julia S.S. <hithwen at gmail.com> wrote:

> Now that you mention it, I'm calling Shellcommand with following env
>
> env={'PYTHONPATH': "${PYTHONPATH}:build/python"
>
> When set up as regular build slave I get this in output:
>
> PYTHONPATH=:build/python::build/python::build/python:
>
> But when is set up as latent I get this:
>
> PYTHONPATH=:build/python:
>
>
> On Sun, Aug 25, 2013 at 4:14 PM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:
>
>> It looks like Python can't find 'nosetests'.  Is that not in PATH in
>> that arrangement?
>>
>> Dustin
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130826/974f3857/attachment.html>