Issue Station
Sign In
Tools hereToolbox

pytorch - ✅(Solved) Fix DISABLED test_eager_equivalence_remainder_backend_inductor_numerics_cuda_float32 (__main__.TestOpInfoPropertiesCUDA) [2 pull requests, 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#180054•Fetched 2026-04-11 06:08:59
View on GitHub
Comments
1
Participants
2
Timeline
64
Reactions
0
Author
praguptapragupta
Participants
praguptapraguptapytorch-bot[bot]pytorch-bot[bot]
Timeline (top)
mentioned ×28subscribed ×28labeled ×7commented ×1

Root Cause

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

PR fix notes

PR #180505: [UT][ROCm][inductor] ROCm-specific XFAILS list for torchinductor_opinfo_property

Description (problem / solution / changelog)

Fixes #180032 Fixes #180033 Fixes #180034 Fixes #180035 Fixes #180036 Fixes #180037 Fixes #180038 Fixes #180039 Fixes #180046 Fixes #180047 Fixes #180048 Fixes #180049 Fixes #180051 Fixes #180053 Fixes #180054 Fixes #180059 Fixes #180060 Fixes #180062 Fixes #180063 Fixes #180069 Fixes #179962

These tests were actually passing on ROCm, but because of the shared (CUDA+ROCm) XFAILED list, those ROCm passes were being turned into failures. This PR adds a ROCm-specific XFAILS list which is a subset of the CUDA XFAILS list.

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

Changed files

  • test/inductor/test_torchinductor_opinfo_properties.py (modified, +65/-17)

PR #180687: [UT][ROCm][inductor] ROCm-specific XFAILS list for torchinductor_opinfo_property

Description (problem / solution / changelog)

Fixes #180032 Fixes #180033 Fixes #180034 Fixes #180035 Fixes #180036 Fixes #180037 Fixes #180038 Fixes #180039 Fixes #180046 Fixes #180047 Fixes #180048 Fixes #180049 Fixes #180051 Fixes #180053 Fixes #180054 Fixes #180059 Fixes #180060 Fixes #180062 Fixes #180063 Fixes #180069 Fixes #179962

These tests were actually passing on ROCm, but because of the shared (CUDA+ROCm) XFAILED list, those ROCm passes were being turned into failures. This PR adds a ROCm-specific XFAILS list which is a subset of the CUDA XFAILS list.

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

Changed files

  • test/inductor/test_torchinductor_opinfo_properties.py (modified, +65/-17)
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 may be resolved by investigating and addressing the issues related to the test_eager_equivalence_remainder_backend_inductor_numerics_cuda_float32 test case.

Guidance

  • Investigate the recent examples of test failures on torch-ci.com to identify patterns or common causes of the failure.
  • Review the test_torchinductor_opinfo_properties.py test file, specifically the TestOpInfoPropertiesCUDA class and the test_eager_equivalence_remainder_backend_inductor_numerics_cuda_float32 test case, to understand the test logic and potential failure points.
  • Consider re-enabling the test and running it locally to reproduce the failure and gather more information about the issue.

Notes

The provided information lacks specific details about the failure, such as error messages or stack traces, which would be necessary to provide a more targeted solution.

Recommendation

Apply workaround: Since the issue is related to a specific test case, a workaround could be to skip this test case or disable it temporarily until the underlying issue is resolved.

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…
#tokenizer error#prompt formatting#chain error#conversation history#tool integration

Still need to ship something?

×6

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

Back to top recommendations

TRENDING