pytorch - 💡(How to fix) Fix DISABLED test_template_epilogue_fusion_occupancy_ratio_test_case_occupancy_ratio_reject_use_async_compile_True (__main__.TestEpilogueFusionStaticAnalysis) [4 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#179694Fetched 2026-04-09 07:50:32
View on GitHub
Comments
4
Participants
1
Timeline
80
Reactions
0
Participants
Timeline (top)
mentioned ×36subscribed ×36commented ×4labeled ×4

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: inductor

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 17 workflow(s) with 68 failures and 17 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_template_epilogue_fusion_occupancy_ratio_test_case_occupancy_ratio_reject_use_async_compile_True
  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_max_autotune.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 @ipiszy @kadeng @muchulee8 @amjames @aakhundov @coconutruben @jataylo

extent analysis

TL;DR

The most likely fix involves re-enabling and debugging the disabled test test_template_epilogue_fusion_occupancy_ratio_test_case_occupancy_ratio_reject_use_async_compile_True in inductor/test_max_autotune.py to address the flakiness.

Guidance

  • Review the provided recent examples and workflow logs to understand the test failures.
  • Follow the debugging instructions to find relevant log snippets and study the logs for the test.
  • Investigate the test file inductor/test_max_autotune.py to identify potential issues causing the flakiness.
  • Consider re-running the test with additional logging or debugging statements to gather more information.

Notes

The provided information suggests that the test is flaky, with 68 failures and 17 successes over the past 6 hours. The debugging instructions and log links should help identify the root cause of the issue.

Recommendation

Apply workaround: Re-enable the test and implement additional logging or debugging to identify and address the root cause of the flakiness. This approach allows for a more targeted investigation and potential 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