ci: keep real-database coverage for both migration resolvers

The Postgres-backed smoke job previously exercised one resolver. Running
the default and the legacy variants in it covers v2 now that it is the
default, without losing v1's coverage.
This commit is contained in:
Yuneng Jiang 2026-09-20 00:50:05 -07:00
parent fac518dbf7
commit 556c7f6b68
No known key found for this signature in database
2 changed files with 4 additions and 3 deletions

View file

@ -1561,9 +1561,10 @@ jobs:
url: tcp://localhost:5432
timeout: "60"
- run:
name: Run legacy migration resolver proxy smoke test
name: Run both migration resolvers against Postgres
command: |
uv run --no-sync python -m pytest -vv \
tests/local_testing/test_basic_python_version.py::test_litellm_proxy_server_config_no_general_settings \
tests/local_testing/test_basic_python_version.py::test_litellm_proxy_server_config_no_general_settings_legacy_resolver
helm_chart_testing:

View file

@ -312,7 +312,7 @@ def test_litellm_proxy_server_config_no_general_settings():
def test_litellm_proxy_server_config_no_general_settings_legacy_resolver():
"""Exercises the opt-out legacy (v1) migration resolver.
Runs in a separate CI job against a local Postgres to avoid collisions
with the default variant when they share a database.
Runs after the default variant in the CI job that provides a local
Postgres, so both resolvers get real-database proxy-boot coverage.
"""
_run_proxy_server_smoke_test(extra_proxy_args=["--use_legacy_migration_resolver"])