Fix test to ignore extra warnings from later versions of distributed. #5600
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.
To fix #5547 problem
It seems that, when dask/distributed version 2023.9.3 --> 2023.11.0, some of our testcases trigger an additional warning about transferring large data to workers (only when using distributed).
I've confirmed that this isn't a new inefficiency : The test takes around 5 seconds via distributed, compared to 1 sec with a threaded or synchronous scheduler, and that performance hit is basically the same both before + after the version change.
So I guess it is just a new warning.
The tests that fail are testing the exact "data fill" warnings issued when saving to netcdf.
This PR gets the offending tests to explicitly ignore any warnings which look like that new message.