TST: add a filter for unactionable warning on windows+numpy2 - #16766

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

devdeps fix was just merged separately, so hopefully after this one, CI will be all green again. 🤞

Thanks!!!

Yes I guess the warning is expected so it must be catched. It would have been better to filter it on the test_update_resized_header method instead of the full class, since it seems to be the only method triggering it. (Or even better around the fits.open context manager).

There were actually 4 test cases triggering it in that class IIRC, which is why I decorated the whole class: it seemed preferable (to me) to avoid duplicating this filter too much, but let me know if you'd rather have more targeted decorators, I'm happy to switch.

From the list in #16765 it happens only in TestHDUListFunctions::test_update_resized_header (which is parametrized) and TestImageFunctions::test_io_manipulation. Applying the filter to all tests in TestHDUListFunctions makes it more difficult to know where this warning is triggered, so yes I would prefer if only this method was decorated.

so yes I would prefer if only this method was decorated.

@neutrinoceros , are you able to issue a follow-up PR? If not, let me know and I can. Thanks!

I'm on it !