-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"sqlite3.OperationalError: database is locked" on CIFS filesystem #476
Comments
I have same problem, have you solve in some way? I launch |
the error is coming out from coverage itself |
but my basic understanding is - that none of the network filesystems offer reliable locking as sqlite would need it |
Same issue here. What is the workaround? |
nope, needs a upstream bug in coverage itself |
Does someone else want to open a bug with coverage? I no longer have access to the system where I first encountered this issue, so I can no longer help test fixes. |
upstream bug created: #594 |
Closing as upstream issue |
I'm confused: the "upstream issue" is in this same repo? |
Same here |
My bad, I meant to create this issue in https://github.com/nedbat/coveragepy. Do you guys think this is the right place? |
That is probably the right place, but if the problem is that SQLite doesn't work on CIFS, then there's not much we're going to be able to do about it. Ideally, you'd have a simple way for us to reproduce it, and even better, an experiment with a simple SQLite db on CIFS, independent of coverage.py. |
Hello is there any update on this or a linked issue in coverage? |
Summary
It seems that
pytest-cov
does not support the CIFS filesystem.Expected vs actual result
I would expect the following to run without error:
$ pytest --cov=.
Instead, I see the following error after all tests are run and before any coverage metrics are reported:
Reproducer
Run
pytest --cov=.
on any CIFS filesystem. I'm encountering this issue on Microsoft Azure.Versions
Config
Code
Should be able to reproduce with any code that contains tests.
The text was updated successfully, but these errors were encountered: