Repository navigation
fix: scan-ring env var may leak across tests on pytest.skip - #3388
andrewwhitecdw wants to merge 1 commit into
Conversation
Greptile SummaryThe PR prevents
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains; the previously reported outer-cleanup issue is fixed by the test’s new Important Files Changed
Reviews (6): Last reviewed commit: "fix: scan-ring env var may leak across t..." | Re-trigger Greptile |
a6da1b8 to
376a997
Compare
|
@greptile-apps thanks for the review. I applied the suggested fix:
The branch has been amended to a single signed-off commit (376a997) and force-pushed. |
|
The fix looks correct. The The overall implementation is clean:
LGTM. |
- Add _scan_env context manager to set/restore NVTE_FUSED_RING_ATTENTION_USE_SCAN around runner.test_backward(). - Make test_scan_env_restored exception-safe on its outer cleanup path. Signed-off-by: Andrew White <andrewwhitecdw@users.noreply.github.com>
2be644e to
d5f6323
Compare
This PR addresses the following issue in
tests/jax/test_distributed_fused_attn.py: scan-ring env var may leak across tests on pytest.skip.Changes
tests/jax/test_distributed_fused_attn.py: scan-ring env var may leak across tests on pytest.skip.Details
Tests
tests/jax/test_distributed_fused_attn.pyGreptile feedback addressed
test_scan_env_restoredintry/finally, so an unexpected assertion or exception no longer leaks the sentinel value into later tests.Local verification:
python3 -m py_compile tests/jax/test_distributed_fused_attn.pypassed. Full pytest execution was not feasible because JAX is not installed in this environment.