Indeed, thanks for pointing this one out.
The test seems to test a shared access in rather a serial order. I wonder if underneath this is actually running as concurrent processes?
The test seems to test a shared access in rather a serial order. I wonder if underneath this is actually running as concurrent processes?
The fundamental cause AFAIK was a SQLite connection was attempting to make a state transition (from one type of locking state to another) which shouldn't be allowed under certain circumstances, but the implementation didn't actually enforce this rule. So the added test really does test the root cause.