This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients pitrou, serhiy.storchaka, vstinner
Date 2017-08-31.22:38:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504219125.54.0.83278427796.issue30776@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine Pitrou: "Victor, it would be nice if you could find a less brutal heuristic."

My current goal is to get green buildbots. If a buildbot is always red, it's hard to notify easily regressions.

Since I rejected "false alarms" from refleak, the refleak buildbot already helped to identify a reference leak regression. I am talking about the Windows Refleak buildbot:

http://buildbot.python.org/all/builders/AMD64%20Windows8.1%20Refleaks%203.x

I'm now working on the x86 Gentoo Refleaks 3.x which raised strange issues like bpo-31217.

I am already making regrtest stricter, but slowly, without breaking buildbots. It's a slow process. That's why I'm to "fix" dangling threads for example. By the way, I'm not done with dangling threads in master yet.

I'm happy if anyone is interested to help me to work on buildbots, which means in practice fixing a new different bug everyday :-) Slowly, the remaining bugs are the most complex ones.
History
Date User Action Args
2017-08-31 22:38:45vstinnersetrecipients: + vstinner, pitrou, serhiy.storchaka
2017-08-31 22:38:45vstinnersetmessageid: <1504219125.54.0.83278427796.issue30776@psf.upfronthosting.co.za>
2017-08-31 22:38:45vstinnerlinkissue30776 messages
2017-08-31 22:38:45vstinnercreate