docs(recipes): note b200-any-training retirement (#1053) in wildcard guide#1475
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
91ce515 to
a2a6c2d
Compare
mchmarny
left a comment
There was a problem hiding this comment.
Doc-only one-line fix; correctly names both -any-training wildcard retirements. Verified against main: only b200-any.yaml/gb200-any.yaml remain (no *-any-training overlays), b200-any-training.yaml was deleted in PR #1053 (commit bbf81769), and the recipe.md#criteria-wildcard-overlays anchor exists. Genuine improvement over the prior text, which named only the GB200 retirement and risked a reader copying the B200 cross-service NCCL pattern back in.
Non-blocking nit: slight reference-type asymmetry — #1052 is the umbrella issue (GB200's implementing PR was actually #1068), while #1053 is a PR. Both auto-link and are relevant, and the #1052 reference predates this PR, so no change needed.
LGTM.
…dcard guide recipe-development.md's criteria-wildcard section credited only the gb200-any-training.yaml retirement (NVIDIA#1052), but b200-any-training.yaml was likewise retired in NVIDIA#1053 (both -any-training wildcards are gone on main; b200-any.yaml / gb200-any.yaml are the live deployment-floor overlays). Name both so recipe authors don't reintroduce the retired B200 cross-service NCCL-threshold pattern. Doc-only.
a2a6c2d to
3e66fd4
Compare
Summary
Fix a stale sentence in the criteria-wildcard section of the recipe development guide: it credited only the
gb200-any-training.yamlretirement (#1052) butb200-any-training.yamlwas likewise retired (#1053). Both-any-trainingwildcards are already gone onmain.Motivation / Context
On
main,recipes/overlays/b200-any.yamlandgb200-any.yamlare the live deployment-floor wildcards — the intent-scoped*-any-training.yamlvariants that previously carried cross-service NCCL thresholds were both retired. The integrator guide still named only the GB200 retirement, which risks a recipe author copying the retired B200 cross-service NCCL-threshold pattern back in. This names both.Fixes: N/A
Related: #1052, #1053, #1004
Type of Change
Component(s) Affected
docs/,examples/)Implementation Notes
One-line edit to
docs/integrator/recipe-development.md. Wording mirrors the contributor-side guidance. The anchor link target (recipe.md#criteria-wildcard-overlays) is unchanged and verified present.Testing
Doc-only: tests, e2e, and Go lint cannot regress from this change. CI lychee link-check covers the touched
docs/**file.Risk Assessment
Rollout notes: N/A
Checklist
git commit -S)