Avoid a flaky warning caused by multi-threaded DB access #3006
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've noticed that we occasionally see a warning about an uncaught exception thrown on one of the worker threads in
test_drawing_from_recursive_strategy_is_thread_safe
.Unfortunately I don't have an example handy, but from memory at least one of the exceptions involved was due to threads not being able to access the database file. Since the database isn't relevant to this test, I've disabled it in the hopes that it will get rid of the warning.