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
gh-94675: Add a regression test for rjsmin re slowdown #94685
base: main
Are you sure you want to change the base?
Conversation
hroncok
commented
Jul 8, 2022
•
edited by bedevere-bot
edited by bedevere-bot
- Issue: gh-94675
I can confirm that when cherry-picked on 3.11.0b3, the test hangs. Will see what happens next. If you have some tips about how to make the tests fail when it takes longer than X seconds, other than using subprocess, please let me know. |
Use multiprocessing to kill the test after SHORT_TIMEOUT.
I've used multiprocessing. |
Misc/NEWS.d/next/Tests/2022-07-08-12-22-00.gh-issue-94675.IiTs5f.rst
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
Thanks, this looks great to me.
If there's concern over the use of multiprocessing, note that "tests that run effectively forever when broken" are a different category to me than "does not take too long" — as long as the test suite does not complete successfully, we'll detect the regression ;-)
Here's a recent example of a regression test that runs forever when regressed: #93815
My concern not about multiprocessing per se. The commit would have broken our WebAssembly buildbots. Neither WASI nor Emscripten support fork() or creation of subprocesses. |