8000 [Break XPU][Inductor UT] Avoid custom op registration conflicts in test_auto_functionalize.py. by etaf · Pull Request #148155 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

[Break XPU][Inductor UT] Avoid custom op registration conflicts in test_auto_functionalize.py. #148155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

test_auto_functionalize.py.

Fix #148148

[ghstack-poisoned]
Copy link
pytorch-bot bot commented Feb 28, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/148155

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 95c78a9 with merge base 6ccbff1 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@etaf etaf changed the title Inductor UT] Avoid custom op registration conflicts in Inductor UT] Avoid custom op registration conflicts in test_auto_functionalize.py. Feb 28, 2025
@etaf etaf requested review from zou3519 and jansel February 28, 2025 03:32
@etaf etaf changed the title Inductor UT] Avoid custom op registration conflicts in test_auto_functionalize.py. [Break XPU][Inductor UT] Avoid custom op registration conflicts in test_auto_functionalize.py. Feb 28, 2025
@pytorchmergebot
Copy link
Collaborator

Starting merge as part of PR stack under #148178

pytorchmergebot pushed a commit that referenced this pull request Mar 1, 2025
…partition for XPU (#148178)

This PR generalized the device-bias code introduced by #147038 . And align the behavior between XPU and CUDA on add + mm + pointwise pattern (for XPU, from addmm + pointwise to mm + fused_add_pointwise) , which fix the failed test case `test_graph_partiton` on XPU.

Pull Request resolved: #148178
Approved by: https://github.com/benjaminglass1, https://github.com/jansel, https://github.com/EikanWang
ghstack dependencies: #148155
majing921201 pushed a commit to majing921201/pytorch that referenced this pull request Mar 4, 2025
majing921201 pushed a commit to majing921201/pytorch that referenced this pull request Mar 4, 2025
…partition for XPU (pytorch#148178)

This PR generalized the device-bias code introduced by pytorch#147038 . And align the behavior between XPU and CUDA on add + mm + pointwise pattern (for XPU, from addmm + pointwise to mm + fused_add_pointwise) , which fix the failed test case `test_graph_partiton` on XPU.

Pull Request resolved: pytorch#148178
Approved by: https://github.com/benjaminglass1, https://github.com/jansel, https://github.com/EikanWang
ghstack dependencies: pytorch#148155
@github-actions github-actions bot deleted the gh/etaf/102/head branch April 2, 2025 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
0