BUG: skip legacy dtype multithreaded test on 32 bit runners#28421
Merged
charris merged 2 commits intonumpy:mainfrom Mar 3, 2025
Merged
BUG: skip legacy dtype multithreaded test on 32 bit runners#28421charris merged 2 commits intonumpy:mainfrom
charris merged 2 commits intonumpy:mainfrom
Conversation
bbcf54f to
0c0bd38
Compare
Member
|
Thanks Nathan. |
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
3 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.
Fixes #28412.
For reasons I don't fully understand,
test_legacy_usertype_cast_init_thread_safetysometimes crashes 32 bit CI runners due to OOM errors. This test spawns a lot of threads but other tests spawn more. The crashes happen when Python exhausts the 4 GB of address space available to the runner, so I think it might depend on factors like the precise memory allocation pattern of the test as well as maybe memory fragmentation in the memory space available to the runner.Rather than trying to track this down more, I just skip the test on 32 bit runners. This crash has only ever been observed there.
While I was at it I did a cleanup (most of the diff) to replace one-off uses of
np.dtype(np.intp).itemsize == 8with a newIS_64BITconstant.