The windows buildbot slaves (cygwin too) are still having problems with the DLL being in use when we start compiling so the compile fails. clean.bat is not called afterwards based on the buildbot log. I don't know if clean fixes the problem. If it does, would this patch fix the problem:
Index: Tools/buildbot/build.bat =================================================================== --- Tools/buildbot/build.bat (revision 45475) +++ Tools/buildbot/build.bat (working copy) @@ -1,4 +1,5 @@ @rem Used by the buildbot "compile" step. +cmd /c Tools\buildbot\clean.bat cmd /c Tools\buildbot\external.bat call "%VS71COMNTOOLS%vsvars32.bat" devenv.com /useenv /build Debug PCbuild\pcbuild.sln If the patch won't fix the problem, is there something else we can do to ensure the python DLL is no longer used regardless of whether the previous test passed or not? If we can get the process handle, can we can subprocess.TerminateProcess()? n _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
