[None][infra] Handle sacct error when checking slurm job status#14367
Conversation
|
/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-Post-Merge-1" |
|
PR_Github #49462 [ run ] triggered by Bot. Commit: |
f017770 to
709b0ed
Compare
|
/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-Post-Merge-1" |
|
PR_Github #49471 [ run ] triggered by Bot. Commit: |
|
PR_Github #49462 [ run ] completed with state |
709b0ed to
73a7c8b
Compare
|
/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-Post-Merge-1" |
|
PR_Github #49471 [ run ] completed with state
|
|
PR_Github #49474 [ run ] triggered by Bot. Commit: |
Signed-off-by: Yuanjing Xue <[email protected]>
73a7c8b to
3ec344c
Compare
|
/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-Post-Merge-1" |
|
PR_Github #49488 [ run ] triggered by Bot. Commit: |
|
PR_Github #49474 [ run ] completed with state |
Signed-off-by: Yuanjing Xue <[email protected]>
|
/bot run --stage-list "GB200-4_GPUs-PyTorch-PerfSanity-Post-Merge-1" |
|
/bot run --stage-list "DGX_B200-PyTorch-1" |
|
PR_Github #49501 [ run ] triggered by Bot. Commit: |
|
PR_Github #49500 [ ] completed with state |
|
PR_Github #49488 [ run ] completed with state |
📝 WalkthroughWalkthroughThe ChangesSlurm job status polling resilience
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #49501 [ run ] completed with state |
|
/bot skip --comment "Single sbatch slurm run is sufficient" |
|
PR_Github #49599 [ skip ] triggered by Bot. Commit: |
|
PR_Github #49599 [ skip ] completed with state |
…IA#14367) Signed-off-by: Yuanjing Xue <[email protected]>
…IA#14367) Signed-off-by: Yuanjing Xue <[email protected]>
Summary by CodeRabbit
Description
Test Coverage
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.