Skip to content

Update torch-xpu-ops commit pin to 3ee2bd2 #150300

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.

Sign up for GitHub

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

Jump to bottom
Closed
chuanqi129 wants to merge 1 commit into from
Closed

Update torch-xpu-ops commit pin to 3ee2bd2 #150300

chuanqi129 wants to merge 1 commit into from

Conversation

@chuanqi129
Copy link
Collaborator

@chuanqi129 chuanqi129 commented Mar 31, 2025

Update the torch-xpu-ops commit to 3ee2bd2f13e1ed17a685986ff667a58bed5f2aa5

@pytorch-bot
Copy link

pytorch-bot bot commented Mar 31, 2025 •
edited
Loading

🔗 Helpful Links

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

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

⏳ No Failures, 54 Pending

As of commit 4abc9fc with merge base bbb9b24 (image):
💚 Looks good so far! There are no failures yet. 💚

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Mar 31, 2025
@chuanqi129
Copy link
Collaborator Author

chuanqi129 commented Mar 31, 2025

XPU CI test passed in https://github.com/pytorch/pytorch/actions/runs/14162199524?pr=150251

This was referenced Mar 31, 2025
Closed
Closed
@EikanWang
Copy link
Collaborator

EikanWang commented Mar 31, 2025

Has passed all test cases on top of PT 2.7

@pytorchbot merge -f

@pytorch-bot
Copy link

pytorch-bot bot commented Mar 31, 2025

❌ 🤖 pytorchbot command failed:

@pytorchbot merge: error: argument -f/--force: expected one argument

usage: @pytorchbot merge [-f MESSAGE | -i] [-ic] [-r [{viable/strict,main}]]

Try @pytorchbot --help for more info.

@EikanWang
Copy link
Collaborator

EikanWang commented Mar 31, 2025

@pytorchbot merge -f "Has passed all test cases on top of PT 2.7"

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Mar 31, 2025

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@EikanWang
Copy link
Collaborator

EikanWang commented Mar 31, 2025

@pytorchbot cherry-pick --onto release/2.7 --fixes "Fix performance regression due to large GRF mode" -c regression

pytorchbot pushed a commit that referenced this pull request Mar 31, 2025
@chuanqi129 @pytorchbot
Update torch-xpu-ops commit pin to 3ee2bd2 (#150300)
7ddfa66 
Update the torch-xpu-ops commit to [3ee2bd2f13e1ed17a685986ff667a58bed5f2aa5](intel/torch-xpu-ops@3ee2bd2)
Pull Request resolved: #150300
Approved by: https://github.com/EikanWang

(cherry picked from commit f74d5d5)
@pytorchbot
Copy link
Collaborator

pytorchbot commented Mar 31, 2025

Cherry picking #150300

The cherry pick PR is at #150301 and it is linked with issue Fix performance regression due to large GRF mode. The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

@pytorchbot pytorchbot mentioned this pull request Mar 31, 2025
Closed
@malfet
Copy link
Contributor

malfet commented Mar 31, 2025

@pytorchbot cherry-pick --onto release/2.7 --fixes "Fix performance regression due to large GRF mode" -c regression

@EikanWang Is there an issue that track this performance regression? How many changes are in this submodule between current and previous pin?

@EikanWang
Copy link
Collaborator

EikanWang commented Apr 1, 2025

@malfet , I misunderstood the intention of the PR. Difference FYI

amathewc pushed a commit to amathewc/pytorch that referenced this pull request Apr 17, 2025
@chuanqi129 @amathewc
Update torch-xpu-ops commit pin to 3ee2bd2 (pytorch#150300)
6375a29 
Update the torch-xpu-ops commit to [3ee2bd2f13e1ed17a685986ff667a58bed5f2aa5](intel/torch-xpu-ops@3ee2bd2)
Pull Request resolved: pytorch#150300
Approved by: https://github.com/EikanWang
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@EikanWang EikanWang EikanWang approved these changes

@gujinghui gujinghui Awaiting requested review from gujinghui gujinghui is a code owner

Assignees

No one assigned

Labels

Merged open source topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@chuanqi129 @EikanWang @pytorchmergebot @pytorchbot @malfet