Message 346467 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	Ali McMaster, jkloth, potomak, vstinner
Date	2019-06-25.01:08:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1561424927.12.0.869779351189.issue37386@roundup.psfhosted.org>
In-reply-to

Content
> 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.

> 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.

History
Date	User	Action	Args
2019-06-25 01:08:47	vstinner	set	recipients: + vstinner, jkloth, potomak, Ali McMaster
2019-06-25 01:08:47	vstinner	set	messageid: <1561424927.12.0.869779351189.issue37386@roundup.psfhosted.org>
2019-06-25 01:08:47	vstinner	link	issue37386 messages
2019-06-25 01:08:46	vstinner	create