pytorch - 💡(How to fix) Fix DISABLED test_strided_leaf_grad_layout_cpu (__main__.TestAutogradDeviceTypeCPU) [2 comments, 1 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#181203Fetched 2026-04-23 07:21:56
View on GitHub
Comments
2
Participants
1
Timeline
34
Reactions
0
Participants
Timeline (top)
mentioned ×14subscribed ×14labeled ×4commented ×2

Root Cause

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

RAW_BUFFERClick to expand / collapse

Platforms: asan, linux, mac, macos, win, windows

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 6 hours, it has been determined flaky in 88 workflow(s) with 176 failures and 88 successes.

Debugging instructions (after clicking on the recent samples link): DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs. To find relevant log snippets:

  1. Click on the workflow logs linked above
  2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
  3. Grep for test_strided_leaf_grad_layout_cpu
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: test_autograd.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @ezyang @albanD @gqchen @nikitaved @soulitzer @Varal7 @bobrenjc93

extent analysis

TL;DR

The most likely fix involves identifying and addressing the root cause of the flaky test test_strided_leaf_grad_layout_cpu by analyzing the workflow logs and test results.

Guidance

  • Analyze the workflow logs by following the provided debugging instructions to identify patterns or errors that may be causing the test to fail.
  • Study the logs from multiple instances of the test run to understand the conditions under which the test fails or succeeds.
  • Investigate the test file test_autograd.py to understand the test case test_strided_leaf_grad_layout_cpu and its dependencies.
  • Check the list of disabled tests at https://hud.pytorch.org/disabled for any related issues or patterns.

Example

No specific code snippet can be provided without further information about the test case or the errors encountered.

Notes

The provided information suggests that the issue is related to a flaky test, but the root cause is not immediately clear. Further analysis of the workflow logs and test results is necessary to identify the cause of the failures.

Recommendation

Apply workaround: Temporarily re-enable the test and run it locally or in a controlled environment to gather more information about the failures and successes, and to identify potential patterns or causes.

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

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