Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Run subprocess-starting tests without pytest-xdist#30264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
jkseppan wants to merge1 commit intomatplotlib:main
base:main
Choose a base branch
Loading
fromjkseppan:separate-subprocess-tests

Conversation

jkseppan
Copy link
Member

I suspect that we are running out of process IDs, or the scheduler
is not letting all subprocesses execute, leading to timeouts in
tests that start subprocesses when there are other tests executing.
This happens often with Python 3.14 tests for some reason.

@rcomer
Copy link
Member

rcomer commentedJul 5, 2025•
edited
Loading

Similar idea at#29981, but it continued using xdist for everything and just moved all subprocess-using tests to a single worker.

@jkseppanjkseppanforce-pushed theseparate-subprocess-tests branch from8b4048c tob817890CompareJuly 5, 2025 10:38
jkseppan added a commit to jkseppan/matplotlib that referenced this pull requestJul 6, 2025
I suspect that we are running out of process IDs, or the scheduleris not letting all subprocesses execute, leading to timeouts intests that start subprocesses when other long-running tests areexecuting. This happens often with Python 3.14 tests for some reason.Put the tests that start a subprocess in a separate loadgroupso that no two of them get executed in parallel.Alternative tomatplotlib#30264.
@jkseppanjkseppanforce-pushed theseparate-subprocess-tests branch fromebaa666 to28eb7a9CompareJuly 6, 2025 06:38
@jkseppan
Copy link
MemberAuthor

Similar idea at#29981, but it continued using xdist for everything and just moved all subprocess-using tests to a single worker.

I tried that and still saw timeout failures, but there's a slightly cleaned-up version in#30267.

I suspect that we are running out of process IDs, or the scheduleris not letting all subprocesses execute, leading to timeouts intests that start subprocesses when other long-running tests areexecuting. This happens often with Python 3.14 tests for some reason.Add a new pytest marker for the tests that start a subprocess attop level, and run these tests in a separate pass withoutpytest-xdist parallelization.
@jkseppanjkseppanforce-pushed theseparate-subprocess-tests branch from48eb0bf to7105892CompareJuly 9, 2025 04:52
@jkseppan
Copy link
MemberAuthor

These still get stuck. Yet another idea: run the tests in separate runner instances (in case we are running out of CPU time or some resource like that on the single instance)#30278

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@jkseppan@rcomer
[8]ページ先頭
©2009-2025 Movatter.jp