-
Notifications
You must be signed in to change notification settings - Fork 1
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
Python segmentation fault on Ubuntu 22.04 CI #8
Comments
It is failing also in the |
I am able to get the test to work by downgrading ipopt to from |
Thanks a lot @traversaro. Any suggestion on how to tackle this? |
I was able to reduce the failing test to:
Do you have any idea on how to enable more casadi and/or ipopt verbosity? |
I reproduced the problem with just a simple ipopt example: https://github.com/casadi/casadi/blob/7f8f055024ed6d86532612f1b706195c7d41074a/docs/examples/python/ipopt_nl.py , so probably we can move the discussion in https://github.com/conda-forge/casadi-feedstock . As a workaround, you can add ipopt=3.14.12=*_0 to the installation instructions/CI to get the tests back on track. |
Sounds good! Thanks a lot! |
As mentioned by @traversaro in conda-forge/casadi-feedstock#91 (comment), a possible workaround is to force |
|
Removed workaround with 42f7999. CI is happy. Thanks a lot @traversaro! Closing |
Just as a future warning, it seems that anyhow something fishy is going on w.r.t. the environ variable not being passed correctly in Python, see conda-forge/casadi-feedstock#93 . The linked bug is on the conda-forge side, but also apt packages on recent Debian and Ubuntu distros (not 22.04, fortunately) seems to be affected. I guess this could affect the correct propagation of |
The latest commit in my development branch failed in CI: https://github.com/ami-iit/hippopt/actions/runs/6160272586
Here the error
I don't think this is related to the code itself. Moreover, it is not failing on Windows and Mac. I was not committing for a while, so maybe there is some dependency change that is causing issues in Linux.
The text was updated successfully, but these errors were encountered: