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 bcap, cooperlees, lukasz.langa, vstinner
Date 2017-08-17.22:21:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
While our CI is getting better everyday, it still has a few flaws.

There is no automated buildbot failure notification to the author and
committer yet because random failures were very common 6 months ago. I
fixed something like 90% of the most common race conditions (in tests but
also in the code), and now the remaining 10% are the least funny ones :-)
My latest report:

In the meanwhile I check manually buildbots output and report bugs and

For gdb, don't worry, the buildbots were fixed quickly, it's fine if the
pre-commit CI missed the issue since gdb changes are rare. I am confident
that we can design a fix without introducing regressions ;-)
Date User Action Args
2017-08-17 22:21:31vstinnersetrecipients: + vstinner, lukasz.langa, cooperlees, bcap
2017-08-17 22:21:31vstinnerlinkissue30983 messages
2017-08-17 22:21:31vstinnercreate