TST: Skip an f2py module test on Windows #26706
Merged
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.
Resolves (staves off) #26703 (comment) by being more consistent with the rest of the F2PY testsuite.
the
util.F2PyTest
helper skips Windows tests, so the test added should also skip on Windows (#25134 again).Looking at the logs it seems like the Windows CI is using the wrong stack though #25000 was why
quadmath
was added for Windows testers, and alsomeson
detects it fine, though it fails to find it while linking. Leaving an extract from the logs here for posterity:The reason why it didn't show up in #26634 which uses a similar test pattern is because that raised an error in
meson
, so we handle aRuntimeError
before trying to link the final module, while here we're trying to catch anImportError
but the Windows CI doesn't import any F2PY modules correctly (since it can't build them).