Skip test_embeddable if compiler cannot be initialized #8686
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It turns out that when
test_embeddablewas marked as passing in Python 3.13 in #8683, there was an error when using Windows x86 or AMD64 after building the wheels - https://github.com/python-pillow/Pillow/actions/runs/12721987647/job/35465533303#step:7:25500Because this problem may occur in a local setup when running the test suite, this PR initializes the compiler (as seen two steps earlier in the error traceback) separately, and if that throws an error, before anything Pillow-related occurs, then the test is skipped.
With this change, the wheels start passing - https://github.com/radarhere/Pillow/actions/runs/12722505250/job/35466599838