I'll update planemo to explicitly check for virtualenv before running
Galaxy and give a very clear error message in this scenario.
I guess I could even make it an explicit dependency of planemo in
setup.py/PyPI - I wonder if it would be okay for planemo to mask the
OS virtualenv when installing
On Thu, 19 Nov 2015 20:35:42 +
John Chilton wrote:
> The latest development release of Galaxy which planemo targets by
> default requires virtualenv to be available. Can you verify that it is
> not available on your machine and install it and try again. I will try
> to
The latest development release of Galaxy which planemo targets by
default requires virtualenv to be available. Can you verify that it is
not available on your machine and install it and try again. I will try
to have planemo give a clearer error in this case if it is indeed the
problem.
-John
On
On Tue, Nov 17, 2015 at 2:48 PM, John Chilton wrote:
> Thanks for the bug report. Somehow Galaxy isn't installing the
> development wheels into the transient Galaxy's virtualenv, I've wiped
> out my planemo caches and I can't reproduce this locally.
Perhaps unrelated, but I
Thanks for the bug report. Somehow Galaxy isn't installing the
development wheels into the transient Galaxy's virtualenv, I've wiped
out my planemo caches and I can't reproduce this locally.
Can you send me the green log messages at the beginning of the test
command as well as the few lines after
Hi,
I have recently upgraded to planemo 0.20.0 and I am getting an error
that I cannot resolve:
Cannot locate xUnit report option for tests - update Galaxy for more
detailed breakdown.
The output from the tool_test_output.json is empty {}
I am using
planemo t --install_galaxy
I am a bit lost