Issue Station
Sign In
Tools hereToolbox

pytorch - 💡(How to fix) Fix DISABLED test_require_stride_order_non_owning (__main__.CPUReproTests) [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#179957•Fetched 2026-04-11 06:11:11
View on GitHub
Comments
1
Participants
2
Timeline
95
Reactions
0
Author
jithunnair-amdjithunnair-amd
Participants
jithunnair-amdjithunnair-amdpytorch-bot[bot]pytorch-bot[bot]
Timeline (top)
mentioned ×44subscribed ×44labeled ×6commented ×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 @pruthvistony @ROCmSupport @jataylo @hongxiayang @naromero77amd @pragupta @jerrymannil @xinyazhang @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 test_require_stride_order_non_owning in test_cpu_repro.py needs to be fixed or re-enabled to resolve the failure on the main branch.

Guidance

  • Investigate the recent failures on torch-ci.com to understand the root cause of the test failure.
  • Review the test case test_require_stride_order_non_owning in test_cpu_repro.py to identify potential issues.
  • Consider re-enabling the test and running it locally to reproduce and debug the failure.
  • Check if there are any platform-specific issues related to the rocm platform that could be causing the test to fail.

Notes

The issue lacks specific technical details, so a thorough investigation of the test failure is necessary to determine the root cause and develop a fix.

Recommendation

Apply workaround: Re-enable the test and debug the failure locally to understand the root cause and develop a fix, as the issue is currently blocking the main branch.

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