[issue31611] Tests failures using -u largefile when the disk is full

2018-05-29 Thread STINNER Victor
STINNER Victor added the comment: According to Serhiy's comment, largefile shouldn't be used with less than 2 GB of free disk space. It was my fault, it's not a bug ;-) -- resolution: -> not a bug stage: -> resolved status: open -> closed ___

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: largefile - It is okay to run some test that may create huge files. These tests can take a long time and may consume >2GB of disk space temporarily. I understand this as 2GB is a minimum free disk

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread STINNER Victor
STINNER Victor added the comment: > "largefile" is for moderately large files, around 2 GiB. largefile creates files larger than 2 GB. Extract of test_largefile: # size of file to create (>2GB; 2GB == 2147483648 bytes) size = 25 My VM has less than 2 GB

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread Jeremy Kloth
Change by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Definitely the test shouldn't be quietly skipped! If you enable the "largefile" resource, but the test can't write large file, this is either a bug in the tested code, or an error in the test, or misconfiguration. We already

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread STINNER Victor
STINNER Victor added the comment: > This is expected behavior, isn't? I would prefer that the test skips itself when the disk is full: on "OSError: [Errno 28] No space left on device". Or maybe largefile resource should be excluded from "all"... at least on

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: This is expected behavior, isn't? -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue31611] Tests failures using -u largefile when the disk is full

2017-09-27 Thread STINNER Victor
New submission from STINNER Victor : I ran the Python test suite on Windows on a freshly installed Python 3.7a1 and I got errors: bpo-31606. I created a separated issue for tests failing because my disk has low free space. On my Windows VM, I have a single 40 GB