test: fix windows init test on 32-bit runners#260
Merged
hkpeprah merged 1 commit intosquare:masterfrom Feb 22, 2026
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #256
Problem
TestLibrary.test_initialize_windowsassumes a 64-bit Python runtime, but it only patchessys.platform. On 32-bit runners (e.g. Arch Linux ARM 32-bit),sys.maxsizeindicates 32-bit and the code correctly selectsJLinkARMinstead ofJLink_x64, causing the test to fail.Solution
Patch
sys.maxsizein the 64-bit Windows test to explicitly model the intended runtime. The 32-bit variant is already covered bytest_initialize_windows_32bit.Testing
PYTHONPATH=. python -m unittest -q