10000 Add XPU device to nested_layer_norm by min-jean-cho · Pull Request #148593 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

Add XPU device to nested_layer_norm #148593

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

Conversation

min-jean-cho
Copy link
Collaborator
@min-jean-cho min-jean-cho commented Mar 5, 2025

Copy link
pytorch-bot bot commented Mar 5, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit 970d6ba with merge base 295f2ed (image):
💚 Looks good so far! There are no failures yet. 💚

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

Copy link
linux-foundation-easycla bot commented Mar 5, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@mlehotskylf
Copy link

/easycla

@lukaszgryglicki
Copy link

/easycla

1 similar comment
@lukaszgryglicki
Copy link

/easycla

@guangyey
Copy link
Collaborator
guangyey commented Mar 7, 2025

@pytorchbot rebase

@guangyey guangyey requested review from albanD, malfet, atalman and ezyang March 7, 2025 03:01
@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased minjean/xpu_nested_layernorm onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout minjean/xpu_nested_layernorm && git pull --rebase)

@pytorchmergebot pytorchmergebot force-pushed the minjean/xpu_nested_layernorm branch from 9c429c4 to f5fbcb9 Compare March 7, 2025 03:02
@albanD albanD requested review from jbschlosser and removed request for albanD March 7, 2025 21:29
@guangyey
Copy link
Collaborator

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

Successfully rebased minjean/xpu_nested_layernorm onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout minjean/xpu_nested_layernorm && git pull --rebase)

@pytorchmergebot pytorchmergebot force-pushed the minjean/xpu_nested_layernorm branch from f5fbcb9 to 970d6ba Compare March 11, 2025 07:09
@guangyey
Copy link
Collaborator

@jbschlosser May I know if you could help review this PR.

@guangyey guangyey added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 11, 2025
Copy link
Contributor
@jbschlosser jbschlosser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! only comment is it would be nice to have a test exercising this

@min-jean-cho
Copy link
Collaborator Author

Thanks @jbschlosser for the review. We have test cases in torch-xpu-ops, where we found the issue f 8000 rom test failure.

@min-jean-cho
Copy link
Collaborator Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request ciflow/xpu Run XPU CI tasks Merged module: xpu Intel XPU related issues open source release notes: xpu release notes category topic: not user facing topic category
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants
0