-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
MemoryError from xmlgen for a big number of tests #3323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
GitMate.io thinks possibly related issues are #641 (MemoryError when writing junitxml for large test suite), #643 (Show number of assertions in test results), #667 (Make tests using random numbers more reproducible), #2936 (-k cannot handle strings containing spaces that start with a number ), and #271 (IOError when writing --junitxml report when run via xdist, sometimes). |
is this a 32 bit python or a 64 bit python? |
I am using 32bit python on Win10 |
It might be I found what is a problem the xml unit (junitxml) was flooded with a huge amount of data 8000*1000 at least line of text +20%. I guess if the xml can hold such big amount of text. Disabling xmlunit (junitxml) or reducing the output sorts the problem |
@andreyv1978 i see, a 32 bit process on windows can at most use 2gb of memory, 3gb in special setups, a) have junitxml write out the reports as they complete a should be straightforward, b is tricky for your use-case a) might already be sufficient since you seem to do ok without junitxml |
yes, for me I can minimize output that writes to junitxml like 1 line per test, which will not exceed about 200000 + 25% lines in total |
Hi
I've not executed this test for a long time, maybe 6 month, but it was running and not failing. The PC was updated multiple times with Win10 updates.
I've updated all pytest packages to make this problem disappear, but still it is failing somewhere I can't find
This is my pytest packages:
The number of tests are 13392 and it is always fails in between 7000 - 9000, running multiple instances
Error from the pytest:
The text was updated successfully, but these errors were encountered: