-
Notifications
You must be signed in to change notification settings - Fork 26.3k
test_execution_trace.py: Use instantiate_device_type_tests to run GPU tests on HPU as well #133975
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/133975
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit c87edef with merge base 28a521e ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Hi @sraikund16 : |
|
Could this diff be stacked on top of this refactor? #134316 |
@aaronenyeshi : It seems like the PR mentioned (#134316 ) provides support of in-tree devices. Since Intel Gaudi (HPU) is an out-of-tree device, we needed a different approach . Please refer to this #126970 as well. |
|
@aaronenyeshi : i agree with @amathewc , we can give the flexibility per file/module. Each device based on the its capability can include itself per module /file (eg : pytorch/test/dynamo/test_model_output.py Line 348 in 1011e0a
we should merge both the changes inline so that its useful for out-of-tree devices such as Intel Gaudi. |
|
Sounds good, cc @sanrise , @briancoutinho , @shengfukevin - please take a look. The changes are related to the execution trace test. |
@aaronenyeshi , @sanrise , @briancoutinho , @shengfukevin : Any update on this ? any further changes needed from our side? |
|
Looks great, just some minor suggestions. @amathewc can you rebase on viablestrict branch, that should ensure all the checks will be passing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
|
@aaronenyeshi , @sanrise , @briancoutinho , @shengfukevin : Removed the extra lines as per review comments. |
|
@shengfukevin , @sanrise , @sraikund16 : Any further changes required from our side for merging this PR ? |
|
@pytorchbot rebase |
|
You don't have permissions to rebase this PR since you are a first time contributor. If you think this is a mistake, please contact PyTorch Dev Infra. |
|
@amathewc Can you rebase/merge using git and push to the branch to start testing |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
a95c3b3 to
ec51d9f
Compare
de493e1 to
bf93602
Compare
|
@aaronenyeshi , @sanrise , @briancoutinho , @shengfukevin, @sraikund16 : could you help in rebase/merge this ? Looks like I do not have the permissions. |
|
@pytorchbot merge |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
bf93602 to
d1b61a5
Compare
|
@aaronenyeshi , @sanrise , @briancoutinho , @shengfukevin, @sraikund16 , @jgong5 : Could you help in merging this ? I don't seem to be authorized to merge this. Have fixed all lint related issues. |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchbot merge |
Merge startedYour 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 |
Merge failedReason: 3 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
… tests on HPU as well
|
Successfully rebased |
015dc28 to
c87edef
Compare
|
@pytorchbot merge |
Merge startedYour 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 |
MOTIVATION
We recently integrated support for Intel Gaudi devices (identified as 'hpu') into the common_device_type framework via the pull request at #126970. This integration allows tests to be automatically instantiated for Gaudi devices upon loading the relevant library. Building on this development, the current pull request extends the utility of these hooks by adapting selected CUDA tests to operate on Gaudi devices. Additionally, we have confirmed that these modifications do not interfere with the existing tests on CUDA devices.
CHANGES