pytorch - 💡(How to fix) Fix DISABLED test_determinism_log1p_backend_inductor_default_cuda_float32 (__main__.TestOpInfoPropertiesCUDA) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#180040Fetched 2026-04-11 06:09:23
View on GitHub
Comments
1
Participants
2
Timeline
146
Reactions
0
Author
Timeline (top)
mentioned ×67subscribed ×67labeled ×9added_to_project_v2 ×1

Root Cause

This test was disabled because it is failing on main branch (recent examples).

RAW_BUFFERClick to expand / collapse

Platforms: rocm

This test was disabled because it is failing on main branch (recent examples).

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @jataylo @hongxiayang @naromero77amd @jerrymannil @xinyazhang @mruberry @kurtamohler @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @kadeng @muchulee8 @amjames @aakhundov @coconutruben

extent analysis

TL;DR

The test failure on the main branch for the test_torchinductor_opinfo_properties.py test may be resolved by investigating and addressing the determinism issue with the log1p backend using the inductor on CUDA with float32.

Guidance

  • Review the recent failure examples on torch-ci.com to understand the nature of the test failures.
  • Investigate the test_determinism_log1p_backend_inductor_default_cuda_float32 test case to identify potential causes of non-determinism.
  • Check the inductor configuration and CUDA settings for any inconsistencies or versioning issues that might be contributing to the failures.
  • Consider re-enabling the test and running it with additional logging or debugging to gather more information about the failure.

Notes

The provided information does not include specific details about the error messages or the code changes that led to the test being disabled, which limits the ability to provide a more targeted solution.

Recommendation

Apply workaround: Investigate and address the determinism issue with the log1p backend using the inductor on CUDA with float32, as this is the most direct path to resolving the test failure.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING