.testmondata does not get flushed at exit

[szym]

What is your setup and what steps did you do?

The easiest way to reproduce is to run pytest --testmon in an environment that has:
pytest==8.2.2
pytest-mock==3.14.0
pytest-testmon==2.1.1

I tried to make it even smaller and found that this reduced part of pytest-mock is enough to cause trouble:

from dataclasses import dataclass
from typing import Iterator

@dataclass
class Foo: pass

T = Iterator[Foo]

What was the outcome?
Once this code is loaded by pytest, it no longer deletes the instance of TestmonData and consequently its db (apparently, Python does not promise __del__ will ever be called unless an instance is explicitly deleted). In result, the sqlite connection is not flushed. The .testmondata will still recover on the next run, but when trying to archive it (as part of CI), it makes a bit frustrating to have to carry its -wal and -shm files as well.

What did you expect instead?
.testmondata to be flushed. Probably simplest to makeTestmonData.close_connection() explicitly close the sqlite3 connection.

What is your operating system and it's version please?
macOS 11.7

[szym]

My workaround right now is to add to conftest.py:

import pytest

def pytest_unconfigure(config):
    if hasattr(config, "testmon_data"):
        config.testmon_data.db.con.close()

[jacksongoode]

Is this still working for you? I've found that locally the wal and shm files get cleaned up but not when we run on CI?

[Enkidu-Aururu]

I can still see this error in pytest-testmon 2.1.3.

If I have no .testmondata, I run pytest --testmon (run all tests), then I get empty .testmondata together with shm and wall files.

Adding pytest_unconfigure into my conftest.py helps.