[None][test] Waive TestGemma4MoE::test_bf16 (missing bf16 MMMU reference)#16289
[None][test] Waive TestGemma4MoE::test_bf16 (missing bf16 MMMU reference)#16289dongfengy wants to merge 1 commit into
Conversation
|
/bot run --disable-fail-fast |
|
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)
📝 WalkthroughWalkthroughAdds one scoped skip waiver for the Gemma4MoE BF16 integration test on the DGX H100 four-GPU AutoDeploy configuration due to missing MMMU reference specifications. ChangesIntegration test waiver
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #58837 [ run ] triggered by Bot. Commit: |
|
PR_Github #58837 [ run ] completed with state
|
cda65cd to
a5daf1b
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #58839 [ run ] triggered by Bot. Commit: |
|
PR_Github #58839 [ run ] completed with state
|
|
/bot reuse-pipeline |
|
PR_Github #58840 [ reuse-pipeline ] triggered by Bot. Commit: |
|
PR_Github #58840 [ reuse-pipeline ] completed with state |
…nce) accuracy/test_llm_api_autodeploy.py::TestGemma4MoE::test_bf16 evaluates MMMU with the plain bf16 spec, but references/mmmu.yaml only registers a NVFP4/FP8-KV entry for google/gemma-4-26B-A4B-it (added in NVIDIA#16108), so the accuracy harness raises ValueError (Not registered specs) before scoring. The failure is deterministic and PR-independent: it failed identically in every recent LLM/main/L0_Test-x86_64-Multi-GPU run (builds 2327-2336), blocking pre-merge CI for any PR that triggers the multi-GPU stage. Waive until the bf16 MMMU reference is added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Dongfeng Yu <dongfengy@nvidia.com>
|
/bot run --disable-fail-fast |
a5daf1b to
b418e58
Compare
|
PR_Github #58863 [ run ] triggered by Bot. Commit: |
|
PR_Github #58863 [ run ] completed with state |
|
Superseded: TestGemma4MoE::test_bf16 has been waived on main via #16283 (all platforms, https://nvbugs/6445322), which mergeWaiveList picks up for all PR runs. This PR is no longer needed. |
Summary by CodeRabbit
Description
accuracy/test_llm_api_autodeploy.py::TestGemma4MoE::test_bf16evaluates MMMU with the plain bf16 spec, butreferences/mmmu.yamlonly registers aquant_algo: NVFP4 / kv_cache_quant_algo: FP8entry forgoogle/gemma-4-26B-A4B-it(added in #16108). The accuracy harness therefore raises before scoring:The failure is deterministic and PR-independent: it failed identically in every recent
LLM/main/L0_Test-x86_64-Multi-GPUrun (builds 2327–2336), currently blocking pre-merge CI for any PR that triggers the multi-GPU stage (see also the report on #16108).This PR waives the test until the bf16 MMMU reference is added (or the test is routed to a registered spec). cc @2ez4bz
Test Coverage
Waive-list-only change; no runtime code affected.
mergeWaiveListpicks this up for all in-flight PRs once merged.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.
🤖 Generated with Claude Code