[https://nvbugs/6550099][fix] Raise no-top-k equivalence tolerance - #17998
Conversation
…ove top-p renorm fp32 precision Signed-off-by: Lori Ren <lorir@nvidia.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)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe advanced sampling test now documents nucleus-cutoff nondeterminism, compares per-row probability-mass differences with a ChangesAdvanced sampling validation
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This narrowly raises a test tolerance and removes the related waiver; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run --stage-list DGX_H100-PyTorch-4 |
|
PR_Github #67652 [ run ] triggered by Bot. Commit: |
|
PR_Github #67652 [ run ] completed with state
|
|
/bot run --stage-list DGX_H100-PyTorch-4 |
|
PR_Github #67739 [ run ] triggered by Bot. Commit: |
|
PR_Github #67739 [ run ] completed with state
|
|
/bot run --extra-stage "DGX_H100-PyTorch-4" |
|
PR_Github #67763 [ run ] triggered by Bot. Commit: |
|
PR_Github #67763 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #67786 [ run ] triggered by Bot. Commit: |
|
PR_Github #67786 [ run ] completed with state
|
|
/bot run --stage-list "DGX_H100-PyTorch-4" |
|
PR_Github #67885 [ run ] triggered by Bot. Commit: |
|
PR_Github #67885 [ run ] completed with state
|
|
/bot run --extra-stage "DGX_H100-PyTorch-4" |
|
PR_Github #68057 [ run ] triggered by Bot. Commit: |
|
/bot run --stage-list "DGX_H100-PyTorch-4" |
|
PR_Github #68057 [ run ] completed with state
|
|
PR_Github #68079 [ run ] triggered by Bot. Commit: |
|
PR_Github #68079 [ run ] completed with state
|
|
/bot run --stage-list "DGX_H100-PyTorch-4" --disable-fail-fast |
|
PR_Github #68137 [ run ] triggered by Bot. Commit: |
|
PR_Github #68137 [ run ] completed with state
|
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
/bot run --stage-list "DGX_H100-PyTorch-4" --disable-fail-fast |
|
PR_Github #68203 [ run ] triggered by Bot. Commit: |
|
PR_Github #68203 [ run ] completed with state |
zhaoyangwang-nvidia
left a comment
There was a problem hiding this comment.
Approve with comments.
… total mass, not atol Signed-off-by: Lori Ren <lorir@nvidia.com>
|
/bot run --stage-list "DGX_H100-PyTorch-4" |
|
PR_Github #68672 [ run ] triggered by Bot. Commit: |
|
PR_Github #68672 [ run ] completed with state
|
|
/bot run --stage-list "DGX_H100-PyTorch-4" --disable-fail-fast |
|
PR_Github #68687 [ run ] triggered by Bot. Commit: |
|
PR_Github #68687 [ run ] completed with state |
|
/bot run --disable-fail-fast |
|
PR_Github #68722 [ run ] triggered by Bot. Commit: |
|
PR_Github #68722 [ run ] completed with state |
Dev Engineer Review
test_no_topk_matches_fullto account for FP32 variation at the nucleus cutoff.1e-5to1e-4.tests/integration/test_lists/waives.txt.QA Engineer Review
test_no_topk_matches_full.test-db/orqa/.Description
Root cause: the assertion's tolerance was tighter than the precision of the operator it compares. FULL and NO_TOPK are bit-identical up to the top-p renorm, so nothing in the sampling path differs. At the nucleus cutoff fp32 precision decides whether one token is kept, and that token is worth up to 7.8e-5 of mass in input batch — about 8x the assertion's atol=1e-5. The test asked for more than fp32 offers, so it failed whenever that boundary token moved.
Fixed by raising atol to 1e-4.
Validated on A100: full file passes, 30 consecutive runs of the case pass. The waiver is removed in the fix PR.
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.