fix(ci): add explicit prisma generate before proxy unit tests

The litellm_proxy_unit_testing_part1 and part2 CI jobs rely on
docker/entrypoint.sh to run prisma generate, but this runs under
set +e which silently suppresses failures. Add explicit 'prisma generate'
in the test run command to ensure Prisma binaries are available.

This matches the pattern used by litellm_mapped_tests_proxy_part1/part2
which successfully run prisma generate before pytest.

Co-authored-by: yuneng-jiang <yuneng-jiang@users.noreply.github.com>
This commit is contained in:
Cursor Agent 2026-03-12 08:08:59 +00:00
parent 10fa3d28f6
commit ee03ef74d5

View file

@ -1076,6 +1076,7 @@ jobs:
command: |
pwd
ls
prisma generate
# Run auth tests with parallel execution (test_key_generate_prisma moved to separate job to avoid event loop issues)
python -m pytest tests/proxy_unit_tests/test_auth_checks.py tests/proxy_unit_tests/test_user_api_key_auth.py --cov=litellm --cov-report=xml --junitxml=test-results/junit-part1.xml --durations=10 -n 8 --timeout=300 -vv --log-cli-level=INFO
no_output_timeout: 120m
@ -1183,6 +1184,7 @@ jobs:
command: |
pwd
ls
prisma generate
python -m pytest tests/proxy_unit_tests --ignore=tests/proxy_unit_tests/test_key_generate_prisma.py --ignore=tests/proxy_unit_tests/test_auth_checks.py --ignore=tests/proxy_unit_tests/test_user_api_key_auth.py --cov=litellm --cov-report=xml --junitxml=test-results/junit-part2.xml --durations=10 -n 4 --timeout=300 -vv --log-cli-level=INFO
no_output_timeout: 120m
- run: