Skip to content
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

Test regularly against dependencies #99

Open
pp-mo opened this issue Jan 2, 2025 · 0 comments
Open

Test regularly against dependencies #99

pp-mo opened this issue Jan 2, 2025 · 0 comments

Comments

@pp-mo
Copy link
Owner

pp-mo commented Jan 2, 2025

Because the tests are constructing an env from scratch each time they run,
we are currently relying on ongoing development activity to spot any problems that might arise when new dependency versions are released.

So for instance, we didn't quickly notice the failures when Iris 3.10 introduced problems for us
More worrying, we likewise won't immediately notice if xarray changes so as to break our interface to it (which does involves rather less stable assumptions about xarray)

So, we should introduce a regular-running check of ncdata tests against latest dependencies.

(and N.B. if dependency breakages ever become frequent and get in the way of development, we can follow Iris et al to a known way out : use lockfiles + regular lockfile updates
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant