On Mon, Feb 22, 2021 at 12:51 PM Ivan Pozdeev via Python-Dev <python-dev@python.org> wrote: > IIRC I suggested earlier that buildsbots should be integrated into the PR > workflow in order to make it the contributor's rather than a core > dev's burden to fix any breakages that result from their changes.
Some buildbot worker take 2 to 3 hours per build. Also, it would not scale. Buildbots are not fast enough to handle the high number of PR and PR updates. When there is clear relationship between a buildbot failure and a merged PR, a comment is added automatically showing the failed test and explanation how to investigate the issue. It's there for 2 years thanks to Pablo, and so far, I rarely saw developers paying attention to these failures. They just ignore it. I'm not trying to blame anyone. Contributing to Python requires a lot of free time. I'm only trying to explain in length what does the "maintenance burden" mean in practice, since some people are pretending that supporting a platform is free. Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/KIVBXMBFUF73PKNDOBGRMWJORS2DNXSM/ Code of Conduct: http://python.org/psf/codeofconduct/
