Fix tests to reduce chance of database is locked error #4997
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Added a mechanism to separate database-modifying tests:
1.Created a SYNCHRONOUS() helper function in utils.py to identify tests that modify the database
2.Added a new pytest command-line option (--synchronous) to run these tests separately
3,Modified the conftest.py to handle this separation logic
Modified tests to avoid database locking:
1.Added @pytest.mark.skipif(not SYNCHRONOUS(), reason="...") to tests that modify the database
2.Ensured database-modifying tests use "-u never" flag when appropriate to avoid unnecessary database updates
3.Updated test classes to avoid database updates in parallel test runs