[Python-Dev] Buildbot questions (original) (raw)

Tim Peters tim.peters at gmail.com
Fri Jan 6 04:10:36 CET 2006

[John J Lee]

Might a buildbot running this setup of David Munman's (free MS compiler + NAnt interpreting the MS project file) be useful?

http://groups.google.co.uk/group/comp.lang.python/browsefrm/thread/226584dd47047bb6/1e33ad19197bee20

No comment from me about that (don't know anything about it, and don't have time to learn).

Someone who wants to see a platform exercised needs to volunteer that platform themself (and realize that every stinkin' little step has to be so well defined that the people running the buildbot master can send the exact steps needed to the slave).

... Much though I like SVN, it seems its working copy management still leaves a little to be desired: Even quite recently (fairly sure it was client version 1.2.*, on Win XP) and with read-only checkouts used only for builds, I've still seen it end up in an incorrect state. I suspect 'svn switch' or 'svn up -r xxxxx' was the culprit, though, so perhaps it's not a problem if exactly 'svn up' is the only svn command ever executed on the checkout.

I doubt anyone slings more svn projects, branches and tags than Zope Corp, and I've had no problems with svn on WinXP there except when a project switches from making copies of externals to getting them via svn:externals instead -- and then everyone has problems, regardless of platform. What I have had problems with is PuTTY, and recently discovered that all my months-long "svn+ssh" problems went away after backing off to the older PuTTY 0.57 (and come back again immediately upon switching to 0.58).

Still, perhaps it's wise to wipe the checkout every so often?

I think it is. And while I haven't seen this under MS VC7.1 yet, a few times I caught VC 6.0 failing to recompile after a relevant header file changed. Certainly from-scratch checkout + build should be done before a release.

More information about the Python-Dev mailing list