pytorch - 💡(How to fix) Fix DISABLED test_custom_function_boxed_grads_cleanup_on_error (__main__.TestAutogradWithCompiledAutograd) [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#180521Fetched 2026-04-17 08:21:54
View on GitHub
Comments
2
Participants
1
Timeline
43
Reactions
0
Participants
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: asan, linux

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 125 workflow(s) with 250 failures and 125 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_custom_function_boxed_grads_cleanup_on_error
  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

To resolve the flaky test issue, investigate the test logs by following the provided debugging instructions to identify the root cause of the failures in test_custom_function_boxed_grads_cleanup_on_error.

Guidance

  1. Follow debugging instructions: Click on the workflow logs, expand the Test step, and grep for test_custom_function_boxed_grads_cleanup_on_error to find relevant log snippets.
  2. Analyze log patterns: Study the logs from multiple instances of the test run to identify any patterns or common errors that may be causing the flakiness.
  3. Review test code: Examine the test file inductor/test_compiled_autograd.py to understand the test case and potential areas where the test might be failing.
  4. Check for similar issues: Refer to the list of disabled tests at https://hud.pytorch.org/disabled to see if other tests are experiencing similar issues.

Notes

The provided information does not specify a clear root cause or solution, so a thorough investigation of the logs and test code is necessary to determine the next steps.

Recommendation

Apply workaround: Since the test is flaky and the cause is unknown, temporarily disabling the test or applying a workaround to stabilize the CI pipeline may be necessary until the root cause can be identified and fixed.

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