Unclosed database sqlite3

[JCHacking]

Summary

When I run my tests with the following command:

pytest --html=reports/tests/index.html \
       --junit-xml=reports/tests/junit.xml \
       --cov=src \
       --cov-report term \
       --cov-report html \
       --cov-report xml \
       --cov-fail-under=100 \
       -vv

I receive errors such as:

pytest.PytestUnraisableExceptionWarning: Exception ignored in: <sqlite3.Connection object at 0x0000019009A11B70>

If I try the same command but with only 1 cov-report it works fine. And if I put the previous version of pytest also.

Versions

pytest = 8.4.0 # FAIL
pytest = 8.3.5 # WORK
pytest-cov = 6.1.1

Config

pyproject.toml

[tool.coverage.run]
data_file = "reports/coverage/.coverage"
source = ["src"]
concurrency = ["thread", "multiprocessing"]

[tool.coverage.paths]
source = ["src"]

[tool.coverage.report]
show_missing = true
skip_empty = true
exclude_lines = [
    "pragma: no cover",
    "raise NotImplementedError",
    "if TYPE_CHECKING:",
]

[tool.coverage.html]
directory = "reports/coverage"
title = "Coverage for tests"

[tool.coverage.xml]
output = "reports/coverage/coverage.xml"

[tool.pytest.ini_options]
asyncio_default_fixture_loop_scope = "function"
asyncio_mode = "auto"
pythonpath = ["src"]
testpaths = ["tests"]
python_classes = ""
filterwarnings = [
  "error",
]

[olliesilvester]

I've also ran into this today. Running tests with PYTHONTRACEMALLOC=1 gives

pytest.PytestUnraisableExceptionWarning: Exception ignored in: <sqlite3.Connection object at 0x7fb9cc52bf10>

Object allocated at:
  File "/venv/lib/python3.13/site-packages/coverage/sqlitedb.py", line 53
    self.con = sqlite3.connect(self.filename, check_same_thread=False)

[johnthagen]

Likely related to

• coverage collection fails when using pytest-xdist and pytest 8.4.0 #693

Warnings behavior seems to have changed in Pytest 8.4.0 and this line (which is important for CI to catch new user-generated warnings) now causes problems with pytest-cov.

[tool.pytest.ini_options]
filterwarnings = [
  "error",
]

[ionelmc]

So I've been banging my head against a wall for this one today and I've found out that this only happens if you use paths in coverage config, or multiple reports. This is so strange it seems like a coverage bug.

[JCHacking]

So I've been banging my head against a wall for this one today and I've found out that this only happens if you use paths in coverage config, or multiple reports. This is so strange it seems like a coverage bug.

I have tried to reduce the coverage version but I can't get it to stop happening. So maybe it's a bug that has always been there but was hidden because pytest didn't throw the error.

[ionelmc]

Best workaround for you right now is allowing resourcewarnings to be warnings, eg:

filterwarnings = [
    "error",
    "always::ResourceWarning"
]

[JCHacking]

It works! I'll leave it like this until I don't get this error, which, as you say, seems to be a coverage error.

[ionelmc]

So I've looked more at this and there's nothing I can do from pytest-cov's side because there's no way to safely close those :memory: dbs (leads to data loss). I hope @nedbat might have some ideas (I think coveragepy needs some changes so there's way to safely close those :memory: instances without loosing data).

What I will do for now is implement some feedback text that tells users how to properly configure filterwarnings (idea 3 from #693).

[RonnyPfannschmidt]

Configure the warnings in the plugin

Else people will ignore those forever

[ionelmc]

Ok, see 4c977c7.

[JCHacking]

If I use the issue-693 branch it works fine!!