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 ncoghlan
Recipients flox, loewis, ncoghlan, orsenthil, pitrou, rhettinger
Date 2010-08-13.16:24:59
SpamBayes Score 3.71453e-06
Marked as misclassified No
Message-id <>
Note that the following sequence should work even without changing the buildbot behaviour:
- in one checkin, modify Modules/Setup.dist. The buildbots will pick up this change on their *subsequent* build (as the build triggered by this checkin, so long as it compiles correctly, will trigger the clean step)
- in a latter checkin, make the changes that depend on the new build order

What breaks at the moment is trying to do both of those things in one step, or trying to do the first step while compilation is broken.

Since Antoine's last reversion, a few successful build have gone through so it should be OK to reapply the original patch again.

Longer term, we probably want to run the clean step both before the configure step and after the compile and test steps (even if the compilation fails).
Date User Action Args
2010-08-13 16:25:01ncoghlansetrecipients: + ncoghlan, loewis, rhettinger, orsenthil, pitrou, flox
2010-08-13 16:25:01ncoghlansetmessageid: <>
2010-08-13 16:25:00ncoghlanlinkissue9545 messages
2010-08-13 16:24:59ncoghlancreate