[Buildbot-devel] Fwd: trouble running tests for 0.7.10

Charles Lepple clepple at gmail.com
Sun Mar 1 22:03:02 UTC 2009


On Sun, Mar 1, 2009 at 8:47 AM, Łukasz Jernaś <deejay1 at srem.org> wrote:
> On Sat, Feb 28, 2009 at 7:18 PM, Marcus Lindblom <macke at yar.nu> wrote:
>> Also, can you run the test-suite locally on that slave and see what happens?
>> (i.e. 'trial.py buildbot.test.test_vc.Mercurial')
>
> buildbotslave at r17272:/tmp/buildbot$ trial buildbot.test.test_vc.Mercurial
> Running 5 tests.
> buildbot.test.test_vc
>  Mercurial
> [--snip--]
[...]
> Maybe it has something todo with usepty=0 on my buildbot?

You can approximate "usepty=0" on the command line by redirecting
standard input, output and error to/from non-tty file descriptors.

Something like the following should work:

trial buildbot.test.test_vc.Mercurial < /dev/null 2>&1 | tee log.txt

If it has something to do with process groups, I think you can add a
"nohup" to the beginning of the command to test that theory. However,
you might need to wrap the whole thing in a "nohup sh -c '...'".

-- 
- Charles Lepple




More information about the devel mailing list