This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, jkloth, loewis, python-dev, steve.dower, tim.golden, zach.ware
Date 2014-07-08.23:49:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404863368.31.0.110676891973.issue21907@psf.upfronthosting.co.za>
In-reply-to
Content
I'm seeing an apparent side-effect of the new clean script (or it seems to correlate).  Since it started running, the Windows buildbots (both 7 and XP) seem to always perform a full clone of the master repository for each build rather than just a pull/update.  That's a noticeable performance difference (15-20 minutes per clone rather than the more typical 1-2 minutes for pull/update) and seems like it should be unnecessary.

I'm not quite sure how the buildbot task makes the decision between the two approaches, but could the new clean be removing a file that's relevant to how the decision is made?
History
Date User Action Args
2014-07-08 23:49:28db3lsetrecipients: + db3l, loewis, tim.golden, jkloth, python-dev, zach.ware, steve.dower
2014-07-08 23:49:28db3lsetmessageid: <1404863368.31.0.110676891973.issue21907@psf.upfronthosting.co.za>
2014-07-08 23:49:28db3llinkissue21907 messages
2014-07-08 23:49:27db3lcreate