pytorch - 💡(How to fix) Fix DISABLED test_ifft_norm_forward (__main__.TestFFT1D) [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#182112Fetched 2026-05-02 05:27:08
View on GitHub
Comments
2
Participants
1
Timeline
38
Reactions
0
Participants
Timeline (top)
mentioned ×16subscribed ×16labeled ×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: 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 21 workflow(s) with 42 failures and 21 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_ifft_norm_forward
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: torch_np/numpy_tests/fft/test_pocketfft.py

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

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @kadeng @amjames @Lucaskabela @jataylo @azahed98

extent analysis

TL;DR

To address the flaky test issue, re-enable the test and analyze the workflow logs to identify the root cause of the failures.

Guidance

  • Re-enable the test in torch_np/numpy_tests/fft/test_pocketfft.py to gather more information about the failures.
  • Follow the provided debugging instructions to find relevant log snippets by grepping for test_ifft_norm_forward in the workflow logs.
  • Study the logs from multiple instances of the test run to identify patterns or common errors that may be causing the flakiness.
  • Check the recent examples and workflow logs for more context.

Notes

The issue lacks specific technical details about the test failures, so a more detailed analysis of the logs is necessary to determine the root cause.

Recommendation

Apply workaround: Re-enable the test and analyze the logs to identify the root cause, as the test is currently disabled due to flakiness, and CI is green but may not reflect the actual issue.

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