You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's super weird: on github's CI server, the compilation fails [only] on python 3.7.
Failure happens at the last linking step (the extension files that binds the c++ code to python): the linker cannot find the python library libpython3.7m even though the python lib directory is correctly specified (/opt/hostedtoolcache/Python/3.7.9/x64/lib). Or maybe it isn't... (why is it not -L?)
* compilation is tested on a matrix of Python x PyTorch x CUDA versions (only on ubuntu for the moment) and triggered when c++/cuda files change (or when setup.py changes)
* tests are run on two versions of PyTorch (on cpu only since the servers do not have a gpu) and triggered when any of the library files change (nitorch/**)
* I had to disable one test that failed (grid_grad -> see #29)
* I also had to disable compilation on Python 3.7 which fails weirdly (see #30)
* Compilation on mac and windows is not there yet (needs a lot more work)
It's super weird: on github's CI server, the compilation fails [only] on python 3.7.
Failure happens at the last linking step (the extension files that binds the c++ code to python): the linker cannot find the python library
libpython3.7m
even though the python lib directory is correctly specified (/opt/hostedtoolcache/Python/3.7.9/x64/lib
). Or maybe it isn't... (why is it not-L
?)Here's what happens on 3.6 (which does not fail):
I have disabled the tests on python 3.7 in the meantime
The text was updated successfully, but these errors were encountered: