-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Migrate tk backend tests into subprocesses #18261
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate tk backend tests into subprocesses #18261
Conversation
I'll take the liberty of converting to draft until you are done experimenting. Feel free to convert back... |
9156b85
to
1b3d407
Compare
It seems to be working; you'll need to rebase to get the docs CI working, and also fix the flake8 issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, flake8 has some complaints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only question is why sometimes you check subprocess.TimeoutExpired
and sometimes subprocess.CalledProcessError
?
Also, we prefer rebase over merge. |
Try to isolate suspected interactions between tests
add note to continue the concept going forward
fa60aa9
to
030943d
Compare
@QuLogic The timeout checks should be there consistently, since you mention it, but some of the tests are better off to check the content of stdout or stderr before checking the return code. Hopefully the new comments make this clear! Also rebased as requested. |
Thanks @richardsheridan , I really appreciate your work on hardening the tk code! |
PR Summary
This PR is a first attempt to fix #18246. Try to isolate suspected interactions between tests by using subprocesses liberally. The argument against this might be that subprocess tests are computationally expensive and we might better track down the weird interactions. I'm happy to go with this or try a different idea!
Eagerly making the pull request to engage CI.
PR Checklist