pytorch - 💡(How to fix) Fix DISABLED test_vmap_over_vmap_captured (__main__.FuncTorchHigherOrderOpTestsWithCompiledAutograd) [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#180439Fetched 2026-04-17 08:22:37
View on GitHub
Comments
2
Participants
1
Timeline
44
Reactions
0
Participants
Assignees
Timeline (top)
mentioned ×18subscribed ×18labeled ×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: linux, slow

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 39 workflow(s) with 78 failures and 39 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_vmap_over_vmap_captured
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: inductor/test_compiled_autograd.py

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

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @kadeng @muchulee8 @amjames @chauhang @aakhundov @coconutruben @jataylo

extent analysis

TL;DR

The test test_vmap_over_vmap_captured is failing intermittently in CI, and to fix it, we need to investigate the logs and identify the root cause of the flakiness.

Guidance

  • To start debugging, follow the provided instructions to find relevant log snippets by clicking on the workflow logs, expanding the Test step, and grepping for test_vmap_over_vmap_captured.
  • Study the logs from multiple instances of the test run to identify any patterns or common errors that may be causing the flakiness.
  • Review the test file inductor/test_compiled_autograd.py to understand the test case and potential areas where the issue may be occurring.
  • Check the list of disabled tests at https://hud.pytorch.org/disabled to see if there are any related issues or known problems that may be contributing to the flakiness.

Notes

The issue is specific to the Linux platform, and the test is failing intermittently, which suggests that the problem may be related to environmental or timing issues.

Recommendation

Apply workaround: Since the test is flaky and the CI is green, it's likely that the issue is not consistently reproducible, and a workaround may be necessary to stabilize the test. Further investigation is needed to determine the root cause and develop a permanent fix.

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_vmap_over_vmap_captured (__main__.FuncTorchHigherOrderOpTestsWithCompiledAutograd) [2 comments, 1 participants]