STINNER Victor <vstin...@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 <rep...@bugs.python.org> <https://bugs.python.org/issue37386> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
