Zachary Ware added the comment:
This should be fixed by #21907 for 3.5, at least; other versions can either
have #21907 backported (in whole or in part), or continue to live with it (like
they have for the past 4 years).
--
assignee: - zach.ware
resolution: - fixed
stage: -
Mark Lawrence added the comment:
@Steve I'm assuming that this is covered by the work you're doing for 3.5
builds, am I correct?
--
components: +Windows
nosy: +BreamoreBoy, steve.dower
versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2
___
: [issue9973] Sometimes buildbot fails to cleanup working copy
Mark Lawrence added the comment:
@Steve I'm assuming that this is covered by the work you're doing for 3.5
builds, am I correct?
--
components: +Windows
nosy: +BreamoreBoy, steve.dower
versions: +Python 3.4, Python 3.5 -Python
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
nosy: +zach.ware
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9973
___
___
Python-bugs-list
Zachary Ware added the comment:
The real simple method here would be to replace clean[-amd64].bat with a call
to kill_python_d (if it exists), followed by an hg --config extensions.purge=
purge --all. That ought to give as much of a guarantee of a clean slate as
possible, with the added
Antoine Pitrou pit...@free.fr added the comment:
As far as I can tell, the same change also needs to be done in build-amd64.bat
and clean-amd64.bat.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9973
Antoine Pitrou pit...@free.fr added the comment:
By the way, the order of these lines in clean-amd64.bat looks wrong:
cd PCbuild
@echo Deleting .pyc/.pyo files ...
del /s Lib\*.pyc Lib\*.pyo
--
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
Oh, and the regrtest command line in test-amd64.bat lacks some options (-rwW
-n) compared to test.bat.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9973
David Bolen db3l@gmail.com added the comment:
Probably - it's just a general sequencing change, so I suppose should apply
equally to all platforms. I suppose even better would be to consolidate the
two clean scripts into one (with a parameter for 32 v. 64), but just patching
both is less
Changes by Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp:
Added file:
http://bugs.python.org/file19968/py3k_buildbot_error_in_clean_faze_v2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9973
Changes by Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp:
Removed file:
http://bugs.python.org/file19047/py3k_buildbot_error_in_clean_faze.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9973
David Bolen db3l@gmail.com added the comment:
I wonder if it might be better to have kill_python run at the tail end of
test.bat, since there's a potential window where losing a connection to the
build master might not run the clean step, so still risk blocking a future
build after a
New submission from Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp:
Sometimes, buildbot fails to clean working copy.
/
(snip)
Clean started: Project: _hashlib, Configuration: Debug|Win32
Deleting intermediate and output files for project '_hashlib',
13 matches
Mail list logo
