[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2021-11-09 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> regrtest: when interrupted, temporary directory is not removed ___ Python tracker

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-19 Thread Chris Jerdonek
Chris Jerdonek added the comment: Personally I think the best solution is to have the test framework allocate a single test directory This is partially done. See here: http://hg.python.org/cpython/file/19c74cadea95/Lib/test/regrtest.py#l1810 # Run the tests in a context manager that

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Trent Nelson
New submission from Trent Nelson: All my slaves' /tmp's are polluted with regrtest fluff. I haven't checked yet, but I presume no cleanup is done if a test/run fails. nitrogen% find /tmp -user cpython 2 /dev/null | wc -l 197 netbsd51-x64-1$ find /tmp -user cpython 2 /dev/null | wc -l 142

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread R. David Murray
R. David Murray added the comment: Cleanup on test failure is supposed to be done. Cleanup on crash or buildbot timeout isn't done as far as I know (and that was a concern I had with the changes made to support.TESTFN and the cwd, but I didn't articulate it very well). If you find tests

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Chris Jerdonek
Chris Jerdonek added the comment: To follow up on David's comment, the unit tests in the test suite aren't consistent in their treatment of temp directories (e.g. they don't use a common API or code path). So it may be hard to address this globally short of wiping the entire temp directory

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com: -- nosy: +Arfrever ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15967 ___

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Antoine Pitrou
Antoine Pitrou added the comment: All my slaves' /tmp's are polluted with regrtest fluff. Which regrtest fluff exactly? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15967

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Trent Nelson
Trent Nelson added the comment: All my slaves' /tmp's are polluted with regrtest fluff. Which regrtest fluff exactly? I was being lazy when I wrote that. By regrtest fluff I was referring to lingering files/directories in /tmp, owned by cpython, starting with tmp*. Few examples below.

[issue15967] Slaves don't seem to clean up their /tmp mess if a step fails.

2012-09-18 Thread Trent Nelson
Trent Nelson added the comment: Cleanup on test failure is supposed to be done. Cleanup on crash or buildbot timeout isn't done as far as I know (and that was a concern I had with the changes made to support.TESTFN and the cwd, but I didn't articulate it very well). Ah, yeah, this is