Skip to content

Arm backend: Convert asserts to raise errors in op_mul #10134

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

Merged
merged 2 commits into from
Apr 22, 2025

Conversation

Sebastian-Larsson
Copy link
Collaborator

@Sebastian-Larsson Sebastian-Larsson commented Apr 14, 2025

Asserts are converted to proper raises to ensure graph integrity.

Improve error message.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218

Asserts are converted to proper raises to ensure graph integrity.

Improve error message.

Change-Id: Ifff799651a67811e1dacdb0af5d332dcb7b4b11e
Signed-off-by: Sebastian Larsson <[email protected]>
@Sebastian-Larsson Sebastian-Larsson added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk topic: not user facing labels Apr 14, 2025
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 14, 2025
Copy link

pytorch-bot bot commented Apr 14, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 9346057 with merge base bb60c25 (image):

NEW FAILURE - The following job has failed:

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

Copy link
Contributor

@digantdesai digantdesai left a comment

Choose a reason for hiding this comment

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

Is this a standard behavior across all the ops?

@Sebastian-Larsson
Copy link
Collaborator Author

Is this a standard behavior across all the ops?

Raise error instead of assert? I'm in the process of converting asserts to raise errors where appropriate, so in that case yes it's standard behavior.

@zingo zingo merged commit a4be2e4 into pytorch:main Apr 22, 2025
166 of 167 checks passed
@Sebastian-Larsson Sebastian-Larsson deleted the assert_mul branch May 15, 2025 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm topic: not user facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants