-
Notifications
You must be signed in to change notification settings - Fork 131
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
Tests are failing on Circle because the cached test code uses an ancient fiona #1980
Comments
@bouweandela @jvegasbsc do you mind updating the cached image so we use 21st century software, gents 😁 I am working on a pure-development install test on Github Actions, so we catch testing issues that appear and are not seen by testing with the cached image 👍 |
The image is built from the |
The |
yes you are right @bouweandela - cheers, I have seen the issue with the very old |
That looks fine to me, why would that be a problem? |
well, if the package is used off the roughly latest |
We intentionally run all ESMValTool tests with the latest released version of ESMValCore. This is to provide a stable development environment for diagnostic developers. |
OK well in that case we shouldn't use the image but rather let conda settle its own environment and download esmvalcore from the channel as a dependency; in addition I recommend using the latest master of esmvalcore in a pure dev test like I implemented in that Github Action to see the bleeding edge work fine (maybe no need for that on Circle now that we have it on GA - bump to review that PR) 👍 |
https://app.circleci.com/pipelines/github/ESMValGroup/ESMValTool/4012/workflows/d9967e41-789d-4a98-9493-e1d113a129ea/jobs/41067/steps
Keep calm and update fiona! Don't worry about the the Circle test fails, the
fiona
that gets installed on Circle is1.8.13
which is ancient, the testing suite works perfectly fine with1.8.18
- in fact in ESMValGroup/ESMValCore#885 I have added a note about it saying we may have to switch to install it from conda in the very near future anywayThe text was updated successfully, but these errors were encountered: