-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
[3.12] gh-105699: Re-enable the Multiple-Interpreters Stress Tests (gh-107572) #112483
[3.12] gh-105699: Re-enable the Multiple-Interpreters Stress Tests (gh-107572) #112483
Conversation
…sts (pythongh-107572) (python#107783) We had disabled them due to crashes they exposed, which have since been fixed. (cherry picked from commit f9e3ff1) Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com> Co-authored-by: Łukasz Langa <lukasz@langa.pl> Co-authored-by: T. Wouters <thomas@python.org>
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit b19e0ef 🤖 If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Looks like the various other backports didn't fix all the issues, though buildbot: AMD64 Fedora Stable PRhttps://buildbot.python.org/all/#/builders/52/builds/1218/steps/6/logs/stdio
buildbot: AMD64 FreeBSD14 PRhttps://buildbot.python.org/all/#/builders/1255/builds/34/steps/5/logs/stdio
buildbot: AMD64 RHEL7 Refleaks PRhttps://buildbot.python.org/all/#/builders/18/builds/1511/steps/5/logs/stdio
|
I may bail out on re-enabling the stress tests on 3.12. They are more important on main. |
I suspect that at least gh-110709 would help, though I'm not sure if we'll backport that or not. |
Triage: is this backport still needed? |
I'm going to say no. :) |
We had disabled them due to crashes they exposed, which have since been fixed.
(cherry picked from commit f9e3ff1)
(This is a repeat of gh-107783, which we had to revert.)