Open benoahb opened 3 years ago
Interesting. I know I definitely didn't set up conda environment activation quite correctly, so I can believe that on some platforms system libraries could creep in and create conflicts, especially with the test scripts. I also seem to recall there being possible issues locating the shapemapper base directory when running inside a docker container, but I thought I had resolved that. I don't have the bandwidth to explore this much myself, but if you are able I would be interested to see the output if you add the following lines to internals/test/variant_correction_tests.sh
after line 27, and just run that script in one of the ubuntu containers and see what these commands output.
echo "BASE_DIR: $BASE_DIR"
echo "PYTHONPATH: $PYTHONPATH"
echo 'which python3: '
which python3
echo 'which shapemapper: '
which shapemapper
echo 'which STAR: '
which STAR
exit
Ah okay now I'm seeing my note in line 26 of shapemapper where I hacked around the problem of locating the base directory while inside a docker container by just passing it as an environment variable at build/test time. That's probably at least part of the issue you're encountering. If you need to get it working in an ubuntu docker container, the quickest hack fix is probably to hardcode a path in all of the shell scripts that try to locate THIS_DIR and/or BASE_DIR, or add a line to pass it in as an environment variable.
Hi there,
I would just like to report that I've been trying to set up the pipeline on different distributions of linux (ubuntu 20.04, 18.04, 16.04 or debian 10) and only the last one, debian, worked without failure when running./run_example.sh.
See below for details:
At this point I decided to remove internals/thirdparty and install all dependencies myself using a miniconda3 container and found one single error:
docker container debian 10 (from the miniconda container):