[issue37386] [EASY] test_io: test_large_file_ops() failed on AMD64 Windows7 SP1 3.x with: [Errno 28] No space left on device
STINNER Victor
report at bugs.python.org
Mon Jun 24 21:08:47 EDT 2019
STINNER Victor <vstinner at redhat.com> added the comment:
> To check - do we definitely want to just skip the test if the below OSError is thrown?
Note: I don't propose to ignore any OSError, only if exc.errno == errno.ENOSPC.
> Could we attempt to clean wherever the test is writing to before the test is run/figure out what is using all the space?
Maybe some tests can be enhanced, but that's not directly related to this issue.
In general, Python tests don't leak any resource: memory, files, etc. If there is a leak, it must be fixed.
The test creates a file which can take up to 2 GiB on the disk. It's a big file. I don't think that other tests leak such huge file.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37386>
_______________________________________
More information about the Python-bugs-list
mailing list