-
Notifications
You must be signed in to change notification settings - Fork 39
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
Nightly tests fail #2657
Comments
Thanks @sloosvel shall have a look |
indeed @sloosvel - the test with upstream development packages fails because that test is needing the development branch of iris, at 3.12.0dev at the moment, and that branch needs to satisfy their pin on Dask https://github.com/SciTools/iris/blob/main/requirements/py312.yml which is <2024.9 - iris need to fix this, and we can definitely ask them to hurry up, I might even open a PR there 😁 |
note that test is often failing, and its purpose is exactly that - to fail so that we are alerted to what stuff's going wrong in a few packages that we grab their dev branches (not the stable released versions, that is) |
@schlunma has an issue on this BTW SciTools/iris#6264 |
Since the issue is not on our side, can I continue with the release? Or should this be fixed first? |
totally go ahead, Saskia, plus, I just put in a PR to fix iris' pins SciTools/iris#6312 |
Just in case the Iris folk don't manage to fix their Dask pin before they release Iris 3.12, it might be nice to relax our pin as described in #2654 (comment). That would hopefully also fix the nightly tests. |
We're on it @bouweandela see SciTools/iris#6312 - just encountering some Dask turbulences 😁 |
they be fine, Saskia, one less of an issue for your 2.12 😃 |
Nightly tests failed due to #2654. @valeriupredoi you said that the env picked iris 3.11 but it looks like it's trying to pick iris 3.12 and that is incompatible with the pin on dask
The text was updated successfully, but these errors were encountered: