[Python-Dev] Strategies for debugging buildbot failures?

Benjamin Peterson benjamin at python.org
Mon Jan 19 01:26:49 CET 2009

On Sun, Jan 18, 2009 at 6:25 PM,  <skip at pobox.com> wrote:
>    Mark> Is it acceptable to commit a change (to the trunk or py3k, not to
>    Mark> the release branches) solely for the purpose of getting more
>    Mark> information about a failure?
> I think it would be kind of nice if you could force a buildbot to use a
> specific branch.  You could then check your diagnostic changes in on a
> branch meant just for that purpose.  Once you're done with your changes you
> could simply delete the branch.

You can already do that. Just click on the name of the buildbot, and
then enter the branch you want it to test.


More information about the Python-Dev mailing list