unit tests

13 views
Skip to first unread message

Tyler Reddy

unread,
Apr 24, 2013, 5:10:23 PM4/24/13
to mdnalysis-...@googlegroups.com
Has anyone performed a full unit test on the most recent development build? Running nosetests directly (or even from Python) with multiple cores seems to cause some kind of problem that impedes progress for hours and using a single processor seems to get stuck at a different point (there seems to be a memory leak as well--completely crippled a machine with 6GB of RAM, and steadily rising consumption so far on a machine with 32GB).

I don't think it's supposed to take hours or consume that much memory. I'm using ubuntu 12.04 and running commands like this from testsuite/MDAnalysisTests:

nosetests --processes=1 -v

Oliver Beckstein

unread,
Apr 24, 2013, 5:56:22 PM4/24/13
to mdnalysis-...@googlegroups.com
Hi Tyler,

On 24 Apr, 2013, at 14:10, Tyler Reddy wrote:

> Has anyone performed a full unit test on the most recent development build?

Just tried it on Ubuntu 12.04, 8 GB RAM:

I ran from the MDAnalysisTests/ directory:

nosetests -v
Ran 561 tests in 400.328s

or use from anywhere

python -c 'from MDAnalysis.tests import test; test(label="full", verbose=3, extra_argv=["--exe"])'


> Running nosetests directly (or even from Python) with multiple cores

I haven't had much luck with parallel testing so I tend to always run the tests in single mode.

> seems to cause some kind of problem that impedes progress for hours and using a single processor seems to get stuck at a different point (there seems to be a memory leak as well--completely crippled a machine with 6GB of RAM, and steadily rising consumption so far on a machine with 32GB).

On Mac OS X I did observe pretty high memory consumption (~ 1 GB), which still seems to high, but I can't pinpoint where it is. When writing UnitTests it is important to add cleanup methods the 'del self.universe' or similar.


> I don't think it's supposed to take hours or consume that much memory. I'm using ubuntu 12.04 and running commands like this from testsuite/MDAnalysisTests:
>
> nosetests --processes=1 -v

As I said, I can't reproduce the failure.

Maybe other people can try it and add their experience.

Oliver

--
Oliver Beckstein * orbe...@gmx.net
skype: orbeckst * orbe...@gmail.com

Tyler Reddy

unread,
Apr 25, 2013, 1:37:35 AM4/25/13
to mdnalysis-...@googlegroups.com
It seems that specifying a single process with --processes=1 and discarding the process flag entirely produces different behaviours. Anyways, if I discard the processes flag it appears to do what I'd expect.



--
You received this message because you are subscribed to the Google Groups "MDnalysis discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mdnalysis-discus...@googlegroups.com.
To post to this group, send email to mdnalysis-...@googlegroups.com.
Visit this group at http://groups.google.com/group/mdnalysis-discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




Reply all
Reply to author
Forward
0 new messages