False alarm. The Travis logs includes (but hides) the install output, and
test_mlab was running for me, but I was looking at the wrong line
numbers. Still though, I would be curious as to any differences, but I
can't seem to download the log file.
Ben
On Thu, Jun 26, 2014 at 6:57 PM, Benjamin
Just noticed an oddity with the tests on Travis versus the tests on my
machine. The test log on Travis for a single run has over 10,000 lines.
But, for me, it is over ~4800 lines. At a glance, I can see that test_mlab
is not executed for me, but they are for Travis. I am very suspicious of
the test
So, I just tried comparing memory usage for a plot displayed via show()
versus savefig() as a PNG. It would seem that saving to pngs uses more
memory. Not sure why, though.
Ben
On Jun 4, 2014 12:57 PM, "Eric Firing" wrote:
> On 2014/06/04 6:26 AM, Benjamin Root wrote:
>
>> A theory...
>>
>> If I
On 2014/06/04 6:26 AM, Benjamin Root wrote:
> A theory...
>
> If I remember correctly, the nosttests was set up to execute in parallel
> using the default Multiprocessing settings, which is to have a process
> worker for each available CPU core. Perhaps this might be the crux of
> the issue with so
A theory...
If I remember correctly, the nosttests was set up to execute in parallel
using the default Multiprocessing settings, which is to have a process
worker for each available CPU core. Perhaps this might be the crux of the
issue with so many simultaneous tests running that the amount of mem
> 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
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 keep
