Skip to content

[Inductor] Fix flaky epilogue fusion tests by adding missing tearDown…#3244

Merged
jithunnair-amd merged 1 commit into
release/2.12from
umechand/release_2.12
May 20, 2026
Merged

[Inductor] Fix flaky epilogue fusion tests by adding missing tearDown…#3244
jithunnair-amd merged 1 commit into
release/2.12from
umechand/release_2.12

Conversation

@umechand-amd
Copy link
Copy Markdown

@umechand-amd umechand-amd commented May 20, 2026

…Class (pytorch#180736)

TestPrologueFusion and TestEpilogueFusionStaticAnalysis both use ExitStack in setUpClass to apply config.patch(), but neither defined tearDownClass to close the stack. When TestPrologueFusion runs before TestEpilogueFusionStaticAnalysis in the same process, config values like max_autotune_gemm_backends="TRITON" leak through, removing the aten kernel choice from autotuning and causing test failures.

Fixes pytorch#179693

Pull Request resolved: pytorch#180736
Approved by: https://github.com/Skylion007

Motivation

Technical Details

Test Plan

Test Result

Submission Checklist

Cherry-picked to release/2.10 branch via #3249

Cherry-picked to release/2.9 branch via #3250

…Class (pytorch#180736)

TestPrologueFusion and TestEpilogueFusionStaticAnalysis both use
ExitStack in setUpClass to apply config.patch(), but neither defined
tearDownClass to close the stack. When TestPrologueFusion runs before
TestEpilogueFusionStaticAnalysis in the same process, config values
like max_autotune_gemm_backends="TRITON" leak through, removing the
aten kernel choice from autotuning and causing test failures.

Fixes pytorch#179693

Pull Request resolved: pytorch#180736
Approved by: https://github.com/Skylion007
@jithunnair-amd jithunnair-amd merged commit f7baaad into release/2.12 May 20, 2026
4 checks passed
@jithunnair-amd jithunnair-amd deleted the umechand/release_2.12 branch May 20, 2026 22:31
@jithunnair-amd
Copy link
Copy Markdown
Collaborator

!cherry-pick --onto release/2.11 release/2.10 release/2.9

@rocm-repo-management-api-6
Copy link
Copy Markdown

Can't perform the cherry-pick keyword: unexpected error

Comment processed by Build

@leo-automation
Copy link
Copy Markdown
Collaborator

!cherry-pick --onto release/2.10 release/2.9

@rocm-repo-management-api-6
Copy link
Copy Markdown

Created branch autogenerated/release/2.10_cherry-pick_pr-3244 and #3249. It contains a merge conflict. Please resolve it

Created branch autogenerated/release/2.9_cherry-pick_pr-3244 and #3250. It contains a merge conflict. Please resolve it

Comment processed by Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants