Skip to content

perf(ci): measure unit-shard coverage with the sys.monitoring core #37589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yuneng-berri merged 3 commits into from
Aug 20, 2026
Merged

perf(ci): measure unit-shard coverage with the sys.monitoring core #37589

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e4ffd65
perf(ci): measure unit-shard coverage with the sys.monitoring core
yuneng-berri Aug 20, 2026
2246e42
Merge branch 'litellm_internal_staging' into litellm_/coverage-sysmon…
yuneng-berri Aug 20, 2026
f612493
Merge branch 'litellm_internal_staging' into litellm_/coverage-sysmon…
yuneng-berri Aug 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/workflows/_test-unit-base.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,6 +129,13 @@ jobs:
WORKERS: ${{ inputs.workers }}
RERUNS: ${{ inputs.reruns }}
DIST: ${{ inputs.dist }}
# coverage.py's sys.monitoring backend (PEP 669), the cheapest core it has.
# It is only the default from Python 3.14, and these shards run 3.12, so it
# has to be asked for. Coverage refuses it when branch measurement is on
# (`branch_right_left` needs > 3.14.0a5) and falls back to the slow core with
# a `no-sysmon` warning, so turning on `branch = true` here means giving this
# back until the runners move to 3.14.
COVERAGE_CORE: sysmon
run: |
if [ "${WORKERS}" = "0" ]; then
uv run --no-sync pytest ${TEST_PATH:?} \
Expand Down
Loading