Conversation
Documentation build overview
Show files changed (9 files in total): 📝 9 modified | ➕ 0 added | ➖ 0 deleted
|
| It is your responsibility, as a core developer, to check the automatic | ||
| build results after you push a change to the repository. It is therefore | ||
| important that you get acquainted with the way these results are presented, | ||
| It is the responsibility of core team members to check the automatic |
There was a problem hiding this comment.
This guide is not in the core team section.
There was a problem hiding this comment.
I understand the intent, and it seems to preserve the original meaning, but I wonder if this is actually what we want?
in particular, do we expect non-core-team members to monitor and react to buildbot failures on their own PRs? or is it always the responsibility of the core-team-member that merged the PR?
There was a problem hiding this comment.
do we expect non-core-team members to monitor and react to buildbot failures on their own PRs
IMO, we shouldn't rely on them. If they want to, I don't think anyone is stopping them, but ultimately I think it should fall on the core team.
There was a problem hiding this comment.
in particular, do we expect non-core-team members to monitor and react to buildbot failures on their own PRs?
No. If you're not familiar with buildbot quirks, the failures aren't easy to diagnose.
| click on it to know which commits it corresponds to. Note that | ||
| the buildbot web pages are often slow to load, be patient. | ||
|
|
||
| * The command-line ``bbreport.py`` client, which you can get from |
There was a problem hiding this comment.
This project has not been updated for ten years, I tried it with a few versions but it no longer works.
There was a problem hiding this comment.
CC @ezio-melotti, I think you are the maintainer, based on the commits?
| you. You can also access builder information by clicking on the builder | ||
| status bubbles in the top line. | ||
|
|
||
| If you like IRC, having an IRC client open to the #python-dev-notifs channel on |
There was a problem hiding this comment.
I watched the channel for a week, no updates (whereas in the CPython discord there were several), so I assume it is defunct.
| == CPython 3.3a0 (default:22ae2b002865, Mar 30 2011, 13:58:40) [GCC 4.4.5] | ||
| == Linux-2.6.36-gentoo-r5-x86_64-AMD_Athlon-tm-_64_X2_Dual_Core_Processor_4400+-with-gentoo-1.12.14 little-endian | ||
| == /home/buildbot/buildarea/3.x.ochtman-gentoo-amd64/build/build/test_python_29628 | ||
| Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=1, verbose=0, bytes_warning=2, quiet=0) |
There was a problem hiding this comment.
I updated the example to a more recent one, but this change is not too important, I can revert it.
| It is your responsibility, as a core developer, to check the automatic | ||
| build results after you push a change to the repository. It is therefore | ||
| important that you get acquainted with the way these results are presented, | ||
| It is the responsibility of core team members to check the automatic |
There was a problem hiding this comment.
I understand the intent, and it seems to preserve the original meaning, but I wonder if this is actually what we want?
in particular, do we expect non-core-team members to monitor and react to buildbot failures on their own PRs? or is it always the responsibility of the core-team-member that merged the PR?
| == CPython 3.3a0 (default:22ae2b002865, Mar 30 2011, 13:58:40) [GCC 4.4.5] | ||
| == Linux-2.6.36-gentoo-r5-x86_64-AMD_Athlon-tm-_64_X2_Dual_Core_Processor_4400+-with-gentoo-1.12.14 little-endian | ||
| == /home/buildbot/buildarea/3.x.ochtman-gentoo-amd64/build/build/test_python_29628 | ||
| Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=1, verbose=0, bytes_warning=2, quiet=0) |
Co-authored-by: Victor Stinner <vstinner@python.org>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
See individual comments for details.