RetroSearch Browse

Mon Jan 19 01:25:39 CET 2009 · http://mail.python.org/pipermail/python-dev/2009-January/085160.html

    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.

Skip

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-January/085160.html below:

[Python-Dev] Strategies for debugging buildbot failures?