Monitor usage resulting in repeated printing about pytest-monitor HOT 7 CLOSED

Hello @csheaff

Thanks for reporting. It is a bit weird to me as I do not play at all with capture fixtures nor the way pytest handles logs and prints.
I might be hard to analyze and debug but I'll try to have a look this week prior to the upcoming release of pytest-monitor.

from pytest-monitor.

After some investigations, I think the problem is related to memory_profiler.
The following example illustrates the problem you are experiencing:

import memory_profiler

def foo():
   print('Hello World')

if __name__ == '__main__':
   print(memory_profiler.memory_usage((foo, ()), max_usage=True, retval=True))

This prints the following on my machine:

Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
Hello World
(25.5625, None)

If I remove the memory profiling part from the plugin, the output is as expected. I'll ask for some support to memory_profiler.

Edit: pythonprofilers/memory_profiler#298

from pytest-monitor.

I understand. I'll prioritize the investigation.

from pytest-monitor.

Hello @csheaff , @tobni

I might have found a workaround. memory_profiler collects datas from a dedicated process. For fast enough functions, it repeats the process until (in our case) 4 measures have been done.

I have constrained the collect to perform 1 iteration only but I have no clue regarding eventual impacts on the collected measures.

I will need to compare with previous run on some repos. I'll check that this week.

from pytest-monitor.

Ill just add that it is not only printing that is repeated, the test function actually executed multiple times. This can cause test-failure.

using pytest 6.1, pytest-monitor 1.4.

from pytest-monitor.

Hi @tobni

This is critical indeed. AFAIK, pytest-monitor is not showing up such behavior with previous versions of pytest. I did run it with a set of 7000+ tests and the ELA time remains constant. I'll need to get some time to dive deep into this issue.
May I suggest for now to use pytest 5.X series? Or is this something you can't consider for any reason?

from pytest-monitor.

Downgrading works for my own testing of parts of a test suite, sure, but it is not an option for CI etc. I was hoping pytest-monitor would grant real insight/value in a CI setting.

from pytest-monitor.