Skip to content

Conversation

@ngoldbaum
Copy link
Collaborator

Fixes #158.

"*::test_marker_threads_one PASSED [[]thread-unsafe[]]*",
"*::test_marker_threads_five PASSED*[[]???%[]]",
"*::test_marker_threads_two PASSED*[[]???%[]]",
"*::test_marker_threads_one PASSED*[[]thread-unsafe[]]*",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure why this doesn't happen on CI, but I needed this for the tests to pass locally.

@kumaraditya303
Copy link

3.15 CI is broken because of python/cpython#142928

@ngoldbaum
Copy link
Collaborator Author

Ping @lysnikolaou - this OK with you?

Copy link
Member

@lysnikolaou lysnikolaou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! This reminds me that it probably makes sense to skip everything if configured_num_workers == 1, especially if parallel_threads is removed. But even if it isn't, we can probably figure out a way to count the number of times it's used in the collection pass.

@lysnikolaou lysnikolaou merged commit 1aafa3c into Quansight-Labs:main Dec 23, 2025
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pytest-run-parallel unnecessarily emits gil re-enabled warning

3 participants