mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
0dfc1eec78
tests/proxy_unit_tests/ runs twice on every pull request. The nine alphabetical shards in test-unit-proxy-legacy.yml cover the same directory as the twelve semantic shards in test-unit-proxy-db.yml, and all nine are required checks, so each PR pays for the directory twice before it can merge. The semantic shards are a strict superset. Expanding both matrices against the working tree, the legacy globs collect 58 files while the semantic shards name all 59: test_model_response_typing is a directory and matches none of the test_[a-z]*.py patterns, so the legacy lane has silently skipped it. The semantic workflow also carries its own assert-shard-coverage guard, which fails if a file under that directory is not assigned to a shard, so a new file cannot drop out of CI once the alphabetical fallback is gone. Verified with .github/scripts/assert_ci_coverage.py: 2380 test files have a runner both before and after the deletion. Removing test-unit-proxy-db.yml as well takes the same guard red with 58 orphaned files, which confirms the guard is live and that the semantic shards, not the legacy ones, are what hold the coverage. The nine bare contexts this workflow published (auth-and-jwt, key-generation, proxy-config, proxy-server, proxy-server-extras, proxy-token-counter, proxy-response-and-misc, proxy-user-auth-and-spend, proxy-utils) still need pruning from the guard-internal-staging ruleset, which needs admin rights and is not part of this change |
||
|---|---|---|
| .. | ||
| actions | ||
| codeql | ||
| ISSUE_TEMPLATE | ||
| observatory | ||
| screenshots | ||
| scripts | ||
| workflows | ||
| ci-coverage-allowlist.yml | ||
| CODEOWNERS | ||
| dependabot.yaml | ||
| deploy-on-aws.png | ||
| deploy-on-gcp.png | ||
| deploy-to-aws.png | ||
| FUNDING.yml | ||
| pull_request_template.md | ||
| template.yaml | ||
