ci: gate DynamoCheckpoint deploy tests on snapshot changes only#11046
Conversation
The vLLM/SGLang DynamoCheckpoint deploy test chain previously triggered on the operator, snapshot, or deploy filters (all of which include the shared *ci anchor), so unrelated CI and operator/deploy changes spun up the expensive GPU vCluster setup only to run or skip the checkpoint test. Narrow the entire checkpoint-exclusive chain (operator/snapshot-agent setup, snapshot placeholders, frontend copy, the deploy tests, and cleanup) to gate on the snapshot filter only, and drop *ci from the snapshot filter so CI-only changes no longer trigger it. Add the checkpoint test file to the snapshot filter so edits to the test still run it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
WalkthroughThe ChangesSnapshot CI Filter and Workflow Gating
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
|
Can we also gate on |
…dirs Address review feedback: also trigger the DynamoCheckpoint deploy tests when the shared snapshot module (components/src/dynamo/common/snapshot) or the operator's checkpoint internals (deploy/operator/internal/checkpoint) change, since both feed the checkpoint pipeline. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Good call - added both |
…t-filter # Conflicts: # .github/workflows/pr.yaml
…s only Follow the vLLM/SGLang pattern from #11046 (ci: gate DynamoCheckpoint deploy tests on snapshot changes only): narrow the changed-files gate on every TRTLLM checkpoint job (snapshot-placeholder, operator setup, snapshot-agent, deploy-test, cleanup) from (operator || snapshot || deploy) to (snapshot == 'true'). Also drop the redundant operator.result == 'skipped' branch so the operator-setup gate matches vLLM/SGLang. The snapshot path filter (.github/filters.yaml) already covers tests/deploy/test_dynamocheckpoint.py, so TRTLLM test changes still trigger these jobs. post-merge-ci.yml already gates all three frameworks identically and needs no change. Signed-off-by: Schwinn Saereesitthipitak <schwinns@nvidia.com>
Summary
The vLLM/SGLang DynamoCheckpoint Deploy Test chain previously triggered on the
operator,snapshot, ordeployfilters. All three of those include the shared*cianchor, so any CI change (and any operator/deploy change) spun up the expensive GPU vCluster checkpoint setup — running or skipping the checkpoint test even when nothing checkpoint-related changed.This PR narrows the trigger to the
snapshotfilter only and drops*cifrom that filter.Changes
.github/filters.yaml: remove*cifrom thesnapshotfilter; addtests/deploy/test_dynamocheckpoint.pyso edits to the checkpoint test itself still run it..github/workflows/pr.yaml: narrow the gating from(operator || snapshot || deploy)to(snapshot == 'true')across all 11 checkpoint-exclusive jobs (operator setup, snapshot-agent setup, snapshot placeholders, frontend copy, the deploy tests, and cleanup) — not just the test jobs, so the expensive vCluster setup doesn't run when the test won't.Behavior
deploy/snapshot/**(or the checkpoint test file) → full checkpoint chain runs, as before.post-merge-ci.ymlis unaffected (it has no changed-files gating; checkpoint tests still always run on merges to main).*-build/*-copy-to-acrjobs are untouched; they already includesnapshotin their OR, so a snapshot-only PR still drives the full chain correctly.🤖 Generated with Claude Code
Summary by CodeRabbit