[Python-Dev] OpenBSD buildbot has many failures

[Victor Stinner]

Le mercredi 1 avril 2015, Davin Potts <python at discontinuity.net> a écrit :
>
> I am personally interested in seeing all tests pass on OpenBSD and am
> willing to put forth effort to help that be so.


Great!


> I would be happy to be added to any issues that get opened against
> OpenBSD.


You can do a search in bugs.python.org. If I recall recorrectly, there are
only a few open issues.


> That said, I have concerns about the nature of when and how these failures
> came about — specifically I worry that other devs have committed the
> changes which prompted these failures yet they did not pay attention nor
> take responsibility when it happened.


That's the purpose of my previous email. If the buildbot is always red,
nobody will check it anymore.

I'm quite sure that the current OpenBSD 5.5 was always red since its setup.
Sometimes, I try to fix some isssues.

Fixing OpenBSD issues usually means install OpenBSD at home because most
issues are specific to OpenBSD. Even for LibreSSL, OpenBSD behaves
differently (on the version number) than FreeBSD.

Having monitored certain buildbots for a while to see how the community
> behaves and devs fail to react when a failure is triggered by a commit, I
> think we should do much better in taking individual responsibility for
> prompting these failures.


When I started to work on Python, I was surprised to not get emails from
buildbots.

There are different issues. Dome buildbots are always red. Threre are still
many sporadic issues: temporary network failures seen as bugs, threads
issues. Multiprocessing issues. Recently, I saw some rare asyncio issues.

So we reduce the number of these issues before spaming developers.

Currently, there is an IRC bot on #python-dev which notify when buildbot
color changes. Or sometiles I chceck the huge waterfall page. By the way,
it became difficult to browse this page because there are too many offline
buildbots.

Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150401/39bd2757/attachment.html>