Skip to content

Conversation

@PatrykWilczewski
Copy link
Contributor

Extension of the condition allowing the cpu scalar to be moved to specific devices.

This fixes an HPU specific error:
torch._dynamo.exc.BackendCompilerFailed: backend='aot_hpu_training_backend' raised: RuntimeError: Expected valueto be on same device asaWhile executing %masked_fill : [num_users=1] = call_method[target=masked_fill](args = (%matmul, %expand_as, %tensor), kwargs = {})

On the HPU in eager mode the problem doesn't occur because the pytorch's implementation is not used then.

@pytorch-bot
Copy link

pytorch-bot bot commented Jun 4, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 204568c with merge base 8f70bf7 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@PatrykWilczewski
Copy link
Contributor Author

@pytorchbot label "topic: not user facing"

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Jun 4, 2024
@bsochack
Copy link

bsochack commented Jun 4, 2024

@cpuhrsch could you please review the change?

@zou3519 zou3519 requested a review from cpuhrsch June 5, 2024 02:18
@zou3519 zou3519 added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 5, 2024
@PatrykWilczewski PatrykWilczewski requested a review from jgong5 June 12, 2024 07:22
@jgong5
Copy link
Collaborator

jgong5 commented Jun 13, 2024

hi @cpuhrsch: any comment on this PR? Is it good for landing?

@PatrykWilczewski
Copy link
Contributor Author

Rebased to latest main branch

@bsochack
Copy link

@cpuhrsch any comments? is it possible to merge this patch?

@bsochack
Copy link

bsochack commented Jul 2, 2024

@pytorchbot rebase

@pytorch-bot
Copy link

pytorch-bot bot commented Jul 2, 2024

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.

@PatrykWilczewski
Copy link
Contributor Author

@pytorchbot rebase

@pytorch-bot
Copy link

pytorch-bot bot commented Jul 3, 2024

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.

@PatrykWilczewski
Copy link
Contributor Author

Hi @cpuhrsch
Could you please take a look at this PR and if you have no comments merge it?

@jgong5 jgong5 requested a review from ezyang July 23, 2024 01:03
@ezyang
Copy link
Contributor

ezyang commented Jul 25, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jul 25, 2024
@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

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@ezyang
Copy link
Contributor

ezyang commented Jul 25, 2024

@pytorchbot merge -f "bypass rocm queue"

@pytorchmergebot
Copy link
Collaborator

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

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 Merged open source topic: not user facing topic category triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants