[CI] Shard long misc test groups - #52346
Conversation
|
This pull request has merge conflicts that must be resolved before it can be |
Assisted-by: AI Signed-off-by: Kevin Luu <51931015+khluu@users.noreply.github.com>
Signed-off-by: Kevin Luu <51931015+khluu@users.noreply.github.com>
335d833 to
e466477
Compare
Signed-off-by: Kevin Luu <51931015+khluu@users.noreply.github.com>
|
Targeted build #86571 exposed a real sharding bug in V1 Sample + Logits: applying pytest sharding to each small file separately left some shard/file pairs with zero nodes, and pytest correctly exited 5. Commit 293dab6 fixes that by collecting the whole group in one pytest invocation before partitioning it. The other changed groups in the build passed: CPU async 16m21s; V1 Core shards 14m34s / 15m46s / 22m18s / 18m55s / 13m39s. A targeted V1 Sample rerun is pending. |
Signed-off-by: Kevin Luu <51931015+khluu@users.noreply.github.com>
|
Follow-up from targeted build #86585: keep the five pytest paths in separate processes to preserve CUDA/fork isolation. Each command now accepts only pytest exit 5 (an expected empty per-file partition) and still propagates every real test failure. YAML/schema validation, rendered-command |
|
/ci run |
|
✅ Triggered Buildkite CI #86906 for commit |
Replace pytest --num-shards/--shard-id partitioning with separate Buildkite steps per command group, so each job runs a coherent suite: - V1 Sample + Logits -> V1 Sample, V1 Logits + Oracle - V1 Core + KV + Metrics -> V1 Core, V1 Executor + Worker, V1 KV Offload, V1 KV Connectors, V1 Metrics + LM Eval - CPU Async Engine group -> Params/Env/Tokenizers/Parser, Multimodal + Config, Reasoning + Renderers, Tool Parsers Shared source_file_dependencies lists are factored out with YAML anchors. No parallelism/shard-id logic remains; the LM Eval integration test now runs unconditionally in its own step. Co-authored-by: Kimi Code <noreply@moonshot.cn>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe Buildkite miscellaneous pipeline splits combined V1 and CPU test jobs into smaller jobs. The changes add shared YAML dependency anchors, separate test commands, per-job AMD mirrors, and shorter job timeouts. ChangesMiscellaneous test pipeline
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This PR only reorganizes CI test commands into separate Buildkite steps and preserves AMD mirrors; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/ci run |
|
✅ Triggered Buildkite CI #86987 for commit |
GIT_TERMINAL_PROMPT=0 makes a transient git credential prompt (seen on agent h200-ci-6-19 in build 86987) error immediately instead of hanging the V1 Metrics + LM Eval job until the timeout. Co-authored-by: Kimi Code <noreply@moonshot.cn>
|
This pull request has merge conflicts that must be resolved before it can be |
Resolve conflict in .buildkite/test_areas/misc.yaml: main added a Git HTTP/1.1 env workaround for the flaky LM Eval source install on the monolithic V1 Core + KV + Metrics step. After the command-based split, that install lives only in the V1 Metrics + LM Eval step, so the env block moves there. Co-authored-by: Kimi Code <noreply@moonshot.cn>
|
This pull request has merge conflicts that must be resolved before it can be |
Why
In the 24-hour dashboard window ending 2026-09-01 10:31 UTC:
What changed
Split the long misc test groups into separate Buildkite steps by command rather than by pytest sharding, so each job runs a coherent suite:
Shared
source_file_dependencieslists are factored out with YAML anchors. Noparallelism/--num-shards/--shard-idlogic remains; the LM Eval streaming-correctness integration test now runs unconditionally in its own step instead of being gated on a shard index. Each NVIDIA step keeps its AMD mirror.This consolidates and replaces draft #52348. No merged or active non-draft PR covers these jobs.
Validation
ci-infraBuildkite step pydantic schemabash -npipeline-generatorrun: 641 Buildkite steps, no duplicate keys, all new steps + AMD mirrors render correctlygit diff --checkTargeted CI
TODO: trigger a targeted build on the new steps and record wall times.
This is a draft pending human review. AI assistance was used.
Summary by CodeRabbit