pytorch - 💡(How to fix) Fix DISABLED test_requires_grad_inside_transform_cpu (__main__.TestComposabilityCPU) [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#180966Fetched 2026-04-22 07:43:16
View on GitHub
Comments
2
Participants
1
Timeline
27
Reactions
0
Participants
Timeline (top)
mentioned ×10subscribed ×10labeled ×5commented ×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: dynamo

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 5 workflow(s) with 10 failures and 5 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_requires_grad_inside_transform_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: functorch/test_eager_transforms.py

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

cc @chauhang @penguinwu @Chillee @samdow @kshitij12345

extent analysis

TL;DR

The most likely fix involves investigating and resolving the flakiness in the test_requires_grad_inside_transform_cpu test by analyzing the workflow logs and identifying the root cause of the failures.

Guidance

  • Investigate the workflow logs by following the provided debugging instructions to identify patterns or commonalities among the failures.
  • Study the test file functorch/test_eager_transforms.py to understand the test case and potential areas where flakiness could be introduced.
  • Look for any recent changes or updates that may have contributed to the test becoming flaky.
  • Consider re-enabling the test and running it locally or in a controlled environment to gather more information about the failures.

Notes

The provided information suggests that the test is flaky, but the root cause is not immediately clear. Further investigation is needed to determine the underlying issue.

Recommendation

Apply workaround: Temporarily re-enable the test and run it in a controlled environment to gather more information about the failures, as the root cause is not immediately clear from the provided logs and test file.

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