pytorch - 💡(How to fix) Fix DISABLED test_unary_ufunc_numerical_log10_backend_inductor_numerics_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#180065Fetched 2026-04-11 06:08:40
View on GitHub
Comments
1
Participants
2
Timeline
64
Reactions
0
Author
Timeline (top)
mentioned ×28subscribed ×28labeled ×7commented ×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 @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 can likely be addressed by investigating and resolving the issue with the test_unary_ufunc_numerical_log10_backend_inductor_numerics_cuda_float32 test case.

Guidance

  • Review the recent failure examples on torch-ci.com to understand the nature of the test failure.
  • Investigate the test_unary_ufunc_numerical_log10_backend_inductor_numerics_cuda_float32 test case to identify the root cause of the failure.
  • Check the test configuration and environment to ensure that the ROCm platform is properly set up and configured.
  • Consider re-enabling the test and running it locally to gather more information about the failure.

Notes

The provided information does not include specific details about the test failure, so further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Since the issue is related to a specific test case, it may be possible to workaround the issue by modifying the test case or the test configuration, rather than upgrading to a fixed version (which is not mentioned in the issue).

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