Skip to content

any clue why nosetests might demand having X DISPLAY? #1217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yarikoptic opened this issue Sep 16, 2015 · 3 comments
Closed

any clue why nosetests might demand having X DISPLAY? #1217

yarikoptic opened this issue Sep 16, 2015 · 3 comments
Labels

Comments

@yarikoptic
Copy link
Member

$> DISPLAY= PYTHONPATH=/home/yoh/proj/nipy/nipy-suite/build-area/nipype-0.11.0/debian/python-nipype/usr/lib/python2.7/site-packages MPLCONFIGDIR=/home/yoh/proj/nipy/nipy-suite/build-area/nipype-0.11.0/build nosetests  nipype    
Unable to access the X Display, is $DISPLAY set properly
@chrisgorgo
Copy link
Member

No idea. Could you try with debug?

On Tue, Sep 15, 2015 at 6:46 PM, Yaroslav Halchenko <
[email protected]> wrote:

$> DISPLAY= PYTHONPATH=/home/yoh/proj/nipy/nipy-suite/build-area/nipype-0.11.0/debian/python-nipype/usr/lib/python2.7/site-packages MPLCONFIGDIR=/home/yoh/proj/nipy/nipy-suite/build-area/nipype-0.11.0/build nosetests nipype
Unable to access the X Display, is $DISPLAY set properly


Reply to this email directly or view it on GitHub
#1217.

@oesteban
Copy link
Contributor

I think this is very related (or duplicated) to #1178

But we couldn't reproduce the situation. It must be related to some interfaces using tvtk.

@yarikoptic
Copy link
Member Author

ok -- thanks -- known, thus closing, commented #1178 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants