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

[Benjamin R. <ben...@ou...>]

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 Root <ben...@ou...> wrote:

> 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_mlab run on Travis because it seems to be running multiple times,
> but I can't be sure.
>
> Michael, can I get the test log for one of the recent Travis runs?
>
> Thanks,
> Ben Root
>
>
>
> On Wed, Jun 4, 2014 at 1:49 PM, Benjamin Root <ben...@ou...> wrote:
>
>> 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" <ef...@ha...> wrote:
>>
>>> 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 many simultaneous tests running that the amount of
>>>> memory used at the same time becomes too large. Or, am I thinking of the
>>>> doc build system?
>>>>
>>>> Ben Root
>>>>
>>>
>>> Ben,
>>>
>>> Top shows a single process.  The VM is configured with 2 cores.
>>>
>>> Eric
>>>
>>
>