SourceForge logo
SourceForge logo
Menu

[matplotlib-devel] nosetests: too slow, too much memory

From: Eric F. <ef...@ha...> - 2014年06月01日 08:25:37
Attachments: test_modules.py
Our standard test has gotten out of control. The most serious problem 
is that running a full test suite now fails on a linux VM with 4 
GB--it's out of memory. Half-way through the set, it is already using 
more than 2 GB. That's ridiculous. Running nosetests separately on each 
test module keeps the max reported by top to 1.6 GB, and the max by 
report_memory to 0.5 GB; still quite a bit, but tolerable. (I don't 
know why there is this factor of 3 between top and report_memory.) This 
scheme of running test modules one at a time also speeds it up by a 
factor of 2; I don't understand why.
The script I used for the module-at-a-time test is attached. It is a 
modification of matplotlib.tests().
Are there any nosetest experts out there with ideas about how to 
streamline the standard test routine?
Eric

View entire thread

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /