[Bug]: Order-dependent mismatch in test_nvfp4_gather_grouped_gemm_act_fusion_rubin on SM107
@peaceh-nv is already working on this.
Since Sep 17, 2026.
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
Summary
tests/unittest/_torch/thop/parallel/test_cute_dsl_moe.py::test_nvfp4_gather_grouped_gemm_act_fusion_rubin[1024-1-32-128-relu2] fails on SM107 only when the whole file runs in one pytest process:
Mismatch percentage 0.05% for rtol 1e-4
It passes 3/3 in isolation and when run with only its sibling params. Reproduced in two separate full-file batches on 4x SM107 against main.
Notes
Order dependence points at state carried across tests (autotuner cache, workspace reuse, or a missing synchronization in the Rubin gather/act-fusion grouped GEMM). It may share a root cause with #18335 (bulk-async reduction not awaited before sC reuse in the Rubin fused-MoE finalize kernel), which shows up as an order-dependent illegal memory access in the BF16 finalize path.
Ask
Root-cause with compute-sanitizer --tool memcheck / racecheck on the full file, and add a per-test reset or the missing sync.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.