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

/ missing in files path when testing with --install_galaxy #80

messersc opened this Issue Feb 18, 2015 · 3 comments


None yet
3 participants
Copy link

messersc commented Feb 18, 2015

I noticed a strange thing when debugging my tool.
There is a / missing, so the directory structure gets screwed up and there is unwanted behaviour like left-over tmp directories.


output files:
current working dir:

where /tmp/tmp4NvYcR/galaxy-central-master/ is the tmp Galaxy root.
tmp4NvYcRfiles should (obviously?) be tmp4NvYcR/files/

Is this a bug in Galaxy or planemo?


This comment has been minimized.

Copy link

erasche commented Feb 18, 2015

(I'm not an official source of truth)
I've actually been using that as a feature during my test iterations--I've actually enjoyed being able to back and check the output of commands and when I have tests that fail, compare outputs. That said, you're right, it does leave an unclean /tmp/

jmchilton added a commit that referenced this issue Feb 22, 2015

Implement --no_cleanup option for test & serve commands.
Prevents deletion of temporary files created for/by Galaxy. Might be useful for debugging stuff (#80 (comment)) - probably would be a whole lot more useful for debugging if we also dropped a little shell script in that directory that allowed resuming Galaxy from that state.

@jmchilton jmchilton closed this in f3c374a Feb 22, 2015


This comment has been minimized.

Copy link

jmchilton commented Feb 22, 2015

@messersc thanks for the bug report, should be fixed now and I will do a new release with the fix soon.


This comment has been minimized.

Copy link

erasche commented Feb 22, 2015

@jmchilton thanks for adding the --no-cleanup option to support my use case :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment