coverage: Skip zerver.lib.migrate coverage.

It is only covered when we run migration tests, which we are not
guaranteed to always be able to do.
This commit is contained in:
Alex Vandiver 2023-08-31 13:10:40 +00:00 committed by Tim Abbott
parent d6745209f2
commit 067de6f948
2 changed files with 4 additions and 1 deletions

View File

@ -122,6 +122,9 @@ not_yet_fully_covered = [
# Cannot have coverage, as tests run in a transaction # Cannot have coverage, as tests run in a transaction
"zerver/lib/safe_session_cached_db.py", "zerver/lib/safe_session_cached_db.py",
"zerver/lib/singleton_bmemcached.py", "zerver/lib/singleton_bmemcached.py",
# Only covered when we run migrations tests, which are not
# guaranteed to exist or be runnable
"zerver/lib/migrate.py",
# Branches in Django settings files are hard to test # Branches in Django settings files are hard to test
"zproject/computed_settings.py", "zproject/computed_settings.py",
"zproject/dev_settings.py", "zproject/dev_settings.py",

View File

@ -11,7 +11,7 @@ def do_batch_update(
assignments: List[Composable], assignments: List[Composable],
batch_size: int = 10000, batch_size: int = 10000,
sleep: float = 0.1, sleep: float = 0.1,
) -> None: # nocoverage ) -> None:
# The string substitution below is complicated by our need to # The string substitution below is complicated by our need to
# support multiple PostgreSQL versions. # support multiple PostgreSQL versions.
stmt = SQL( stmt = SQL(