-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change conda-build-version to mamba-version #178
Change conda-build-version to mamba-version #178
Conversation
This is the workaround at the top of the issue now:
|
I'm not seeing any output in the test step. |
I had to change the run steps to a different multi-line syntax. I don't know why what we have in master didn't work. Now the tests are failing, seemingly because the mamba installs of scipy aren't executing. |
The mamba commands don't show output because of the |
Looks like some scipy versions are failing with:
So the recent PR isn't handling imports correctly in some cases. |
I'm guessing this is a mamba install fail, but there is no output so hard to know:
|
Good news is that using mambaforge fixes the first issue. |
I don't understand why I can't see the output from the mamba commands. It is impossible to debug without any information. |
These are the failing builds: mac py 3.10, ipopt 3.12 It seems to fail when scipy is installed. So maybe there isn't a compatible scipy for these envs? |
@brocksam do you know why the output from the mamba install commands is not displayed to stdout? |
I made this conda env file that does Py 3.11 and Ipopt 3.12 on linux: name: cyipopt-fail
channels:
- conda-forge
dependencies:
- cython >=0.26
- ipopt ==3.12.*
- libblas * *netlib
- numpy >=1.15
- pkg-config >=0.29.2
- pytest >=3.3.2
- python ==3.11.*
- scipy >=0.19.1
- setuptools >=39.0
- sphinx then
worked for me. This should be the same combo of packages that fails in CI. |
With the
which doesn't seem to give any more clues. |
This might be related: mamba-org/mamba#2193 |
The |
This could also be a sign to drop Ipopt 3.12 support. |
Ipopt 3.12.13 (last version) was released in April of 2019. Seems reasonable to drop it. |
I'm running Ubuntu 22.10 and it includes Ipopt 3.11.9. So maybe we shouldn't be so hasty in removing 3.12. |
I'm back to conda (solution 2 in the related action issue). And I get more info:
I see now that ipopt is being upgraded when we install scipy. That is likely the problem. |
Apparently |
Here is a new clue from the failing mac build:
Maybe the new scipy versions have this new libfortran requirement that is incompatible with ipopt being build with libfortran4. |
Py 3.11 & Ipopt 3.12 Ubuntu
Py 3.11 & Ipopt 3.12 Mac
Py 3.10 & Ipopt 3.12 Mac
|
Looks like SciPy 1.8 can't be used with Py 3.11:
|
There is some kind of incompatiblities associated with libfortran. I guess it is impossible to have ipopt 3.12 with python 3.11 and get a libfotran that works for both scipy and ipopt. |
I'll never get these hours back. What a nightmare. What we do for that green check mark. |
Try mambaforge variant. Use mamba to install. Remove the pyproject.toml file before installing. Use correct multi line command syntax.
Add mamba list calls. Try the conda experimental sovler solution. Use an explicit install command with all packages, --freeze-installed did not seem to work. Try removing lapack before installing scipy. Make sure only the conda forge channel is used in scipy install. Use SciPy 1.9 with Ipopt 3.12. Try skipping only the builds that have issues with scipy being involved.
032a659
to
7ccf44e
Compare
FYI I squashed things here. Branch history rewritten. |
Gonna go with this, we can edit in other PRs if needed. |
This PR attempts to fix #177 by replacing
conda-build-version
inconda-incubator/setup-miniconda
step of all jobs in all GitHub Actions workflows withmamba-version
, as per conda-incubator/setup-miniconda#116.