Describe the bug Since coverage v5.0.2, I throw an exception during Python 3.6 testing (Python 3.4, 3.5, 3.7, and 3.8 work fine – source).Below is a screenshot of the exception thrown ()This problem does not occur with v5.0.1 ().. Originally I thought this was a Travis CI issue (), but it appears specific to the last release of coverage instead.. To Reproduce, I was able to make it work so I’ll post what I did. I think the cause of the problem is that SQLite locking doesn’t work reliably on NFS filesystems as described in this link.. The answer is also given there and I’ll write the steps in more detail here:, 10/21/2018 · GitHub is where the world builds software. Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and.
reopen The resolution will be deleted. Next status will be ‘reopened’. change ownership to The owner will be changed from Jonas Borgström to the specified user.
You should have searched for duplicates: search:! OperationalError: disk I/O error Duplicate of #6213 , please look there for a detailed explanation of the issue. Modify Ticket, reopen The resolution will be deleted. Next status will be ‘reopened’. change ownership to The owner will be changed from (none) to the specified user.
cur.execute (create table test (name, age)) #fails on server, works on desktop. the result: An empty file.db is created, and I get sqlite3.OperationalError: disk I/O error on the execute command. If I use :memory:, the command works fine.
Worth mentioning is that this will disable rollback.Without journal mode, SQLite does not support atomic transactions (or even transactions at all, for that matter).
