Skip test_save_aggregate_slice
for Numpy 1.25.x and unpin numpy-dev
#2429
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
GlueSerializer
failure/hang first reported in #2353 has now made it into Numpy 1.25, so to keep jobs from just timing out (and burning CI hours), this pins all tests to 1.24.x as a temporary workaround.Alternatively one could skip
test_save_aggregate_slice
conditionally on Numpy >= 1.25, but that would leave that test to be run in only one or two tests – but perhaps better, than lagging by an entire Numpy release with everything else?Might reactivate an
lts
job withnumpy==1.24.*
...Workaround for #2428