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
Failing imports #120
Comments
@djhoese Looks like python-eccodes is build with |
Thanks! I'll try some stuff out. I tried |
Interesting, looks like 2.19.1 fails on my system which had defaulted to 2.20.0. Now to figure out why CI picked up 2.19.1 instead of 2.20. |
I filed a bug on python-eccodes just in case and have forced the version of eccodes on my CI and things seem to be working now. I confirmed that in a build ~24 hours ago eccodes 2.20.0 was installed but something has changed that made the solver choose 2.19.1 now. I'm not sure why and I'm not sure why it is doing that choice on my CI (github incubator action) but not on my local version of conda. I should maybe check versions of conda. Closing for now as I'm not really sure this is eccodes problem. |
Issue:
I have some CI that just started failing last night due to not being able to import python-eccodes. However, I'm unable to reproduce the issue locally so I'm out of ideas for how to debug this. Here is a failing CI job on GitHub:
https://github.com/pytroll/satpy/pull/1563/checks?check_run_id=1957708029
Environment (
conda list
):Conda create/install log is all I can get below.
Environment file here: https://github.com/pytroll/satpy/blob/master/continuous_integration/environment.yaml
Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: