[https://nvbugs/6094208][fix] AutoDeploy: skip bf16 Nemotron-Nano-V3 accuracy test on <80GB GPUs - #14243
Conversation
…accuracy test on <80GB GPUs The Nano 30B bf16 weights alone nearly exceed the memory available on L40-class cards, so the test OOMs in CI even with low-memory overrides applied. Gate the bf16 parametrize entry on >=80GB device memory; fp8/nvfp4 remain gated by their existing architecture markers. Signed-off-by: Gal Hubara Agam <96368689+galagam@users.noreply.github.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 (1)
📝 WalkthroughWalkthroughA single test parameter in the Nemotron accuracy test is updated to include a conditional skip mark. The ChangesTest skip condition for Nemotron bf16 model
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run |
|
PR_Github #48885 [ run ] triggered by Bot. Commit: |
|
PR_Github #48885 [ run ] completed with state |
…accuracy test on <80GB GPUs (NVIDIA#14243) Signed-off-by: Gal Hubara Agam <96368689+galagam@users.noreply.github.com>
Summary by CodeRabbit
Description
The Nano 30B bf16 weights alone nearly exceed the memory available on L40-class cards, so the test OOMs in CI even with low-memory overrides applied. Gate the bf16 parametrize entry on >=80GB device memory; fp8/nvfp4 remain gated by their existing architecture markers.
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.