Hi,
it looks like bug. When job is terminated by exceeded wallclock Galaxy assumes
that job finished normaly and has green status in history. What confuses user
while there are no results or results are broken.
Report from SGE:
05/22/2016 20:16:26| main|o3|W|job 1643894.1 exceeded hard
HI,
Bug in latest Hisat2 tool.
Hisat2 tool version 2.0.3 revision 2d449a1bb5ab does not attempt to
setup the environment in tool_script.sh and job stops with error:
Fatal error: Exit code 127 ()
/home/galaxy/database/jobs_directory/000/497/tool_script.sh: line 9:
hisat2-build: command not
Hi George,
how do you start your container? Anything special in your network settings.
I can not reproduce this with 16.04 and 16.01 and have never seen this
before.
Which version of Docker? Is this under Linux?
I'm a little bit puzzled here.
Sorry,
Bjoern
> Hi Bjorn,
>
> We are using
