Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
[3.11] GH-99729: Unlink frames before clearing them#100047
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Looks good. |
bedevere-bot commentedDec 6, 2022
🤖 New build scheduled with the buildbot fleet by@markshannon for commit5314243 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
I'm curious about "Refleaks" buildbot timings ("Total duration"):
On-going: PPC64LE RHEL7 Refleaks PR (26 min). |
I'm away from my computer for the next hour or so, so feel free to merge when ready. |
What's curious about this? |
vstinner commentedDec 6, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
On Discord,@markshannon wrote that " PPC64LE RHEL7 Refleaks PR" took "forever" :-) |
The problem is not that the individual runs take a long time, but that one overworked machine is running many of them, so collectively they take "forever" (actually a few hours) |
I looked at the latest 10 builds. They waited between 1 second and 30 minutes, and the slowest took 1 hour (Refleaks build, tests took 50 min). |
Uh oh!
There was an error while loading.Please reload this page.
This is a manual backport of the not-yet-merged#100030.
That one should happen first, but I thought I'd get this ready while the buildbots ran.