Teardown duration reported in the following setup (pytest_runtest_logreport)

[Sup3rGeo]

This simple test:

import time
import pytest

@pytest.fixture(scope="module", params=[1, 2])
def fix():
    time.sleep(2)
    yield
    time.sleep(2)

@pytest.mark.parametrize('par', [1, 2])
def test_one(fix, par):
    pass

And this conftest.py file:

def pytest_runtest_logreport(report):
    print(f"Report at {report.when}, with duration {report.duration}")

The prints I get are:

Report at setup, with duration 2.00620698928833
Report at call, with duration 0.0
Report at teardown, with duration 0.0
Report at setup, with duration 0.0
Report at call, with duration 0.0
Report at teardown, with duration 0.0
Report at setup, with duration 4.012362957000732
Report at call, with duration 0.0
Report at teardown, with duration 0.0
Report at setup, with duration 0.0
Report at call, with duration 0.0
Report at teardown, with duration 2.0061838626861572

So, basically, instead of having in the middle of test a teardown with 2 seconds and then a setup with 2 seconds, I have instead a setup of 4 seconds.

Is it normal or a bug?

Windows 10 and python 3.6 venv with only pytest 5.0.1 installed.

[nicoddemus]

Hi @Sup3rGeo!

This is a side-effect of #4871, I'm afraid: fixtures are teardown during setup (when it is decided that a different fixture instance is needed).

I don't think there's a simple solution other than a full refactoring of the teardown mechanism, as discussed in #4871. 😕

[Sup3rGeo]

I see. You tagged this issue as a question, in that case this could be closed.

Or maybe this is indeed a bug and should we tag it as such and leave it opened?

[nicoddemus]

Let's leave it open then; it is linked with #4871, so eventually we can announce it has been solved in the changelog together. 👍