Closed jeromekelleher closed 5 years ago
The problem is down to us pulling in blas from mkl instead of openblas. A workaround for now seems to be to run conda install "blas=*=openblas"
for a new environment.
Will see if it's possible for us to specify that msprime requires blas_openblas, hopefully sorting the mess out.
See also this
The problem is all to do with the solver trying to minimise features. This causes it to pull in packages from defaults, even though they are at higher priority: the conda-forge numpy and GSL packages have the openblas feature, but the defaults ones don't.
Finally tracked the features documentation to here
I think this might be fixed now, after putting in hard requirements to openblas. Would you mind trying the latest package please @alimanfoo? This should be something like msprime-0.6.2-py36hf3f1cc3_3.tar.bz2
Rebuilding environment now with 0.6.2, CI running here: https://github.com/malariagen/binder/pull/33
Hmm, still not quite right I think @alimanfoo. Looks like the solver doesn't like the current requirements somehow, so it won't install the latest build unless you force it with conda install msprime==0.6.2=py36hf3f1cc3_3
. It works fine when you do this though --- very frustrating.
Should be resolved now we're explicitly pulling in openblas.
Issue:
Looks like this is because GSL is being pulled from upstream and not from conda-forge
Originally reported in https://github.com/tskit-dev/msprime/issues/694