Closed krober10nd closed 3 years ago
@nschloe maybe you have some hints as to what may cause an error such as this?
maybe it has to do with the order of the builds?
@nschloe so that was challenging. Turns out the docker for Python 3.8.1 had a conflicting version of virtualenv
which lead to some missing module problem. The solution was to uninstall virtualenv
for 3.8.1.
Anyway, I can add other Python builds too if you like. I'm not sure what you consider to be "well-tested" per your issue #158 since there's literally dozens of Python versions between 3 and 3.9. Please let me know.
I usually go for one per supported Python minor, e.g., 3.6.x, 3.7.y, 3.8.z.
https://github.com/nschloe/dmsh/blob/master/.github/workflows/ci.yml#L27
looks like a server that hosts libopenmpi failed or blocked the simultaneous queries.
You may want to look at github-actions.
You may want to look at github-actions.
Yea this is quite annoying.
ah there's a spacing problem with the 3.6.1 build. I'm just guessing at the syntax here.
this issue with 3.6.1 not finding open MPI is related to the apt-get not having up-to-date package information.
Regardless of GitHub actions or CircleCI I still will need to build things from source unless I create my own docker. It seems that the default Python version dockers provided by CI also were created on old versions of the Debian. I wonder if there is a way to get the older versions of Python on the most recent LTS?
ah so got the 3.6.5 Docker to run but looks like a CPP error now was caught with an older compiler. Interesting. I'll have to activate the docker to see how to repeat the compilation error..