Message300461
| 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 |
<CAMpsgwZDLhrtv8ukPDMt544ar-Zg+iBH=dyTGtanNMvyaFJFQw@mail.gmail.com> |
| In-reply-to |
<1503003021.64.0.447308788387.issue30983@psf.upfronthosting.co.za> |
| Content |
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:
https://haypo.github.io/python-buildbots-2017q2.html
In the meanwhile I check manually buildbots output and report bugs and
regressions.
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 ;-) |
|