Skip to content

Arm backend: Add tosa_spec info to .tosa files #9392

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 3 commits into from
Mar 27, 2025

Conversation

oscarandersson8218
Copy link
Collaborator

@oscarandersson8218 oscarandersson8218 commented Mar 19, 2025

Arm backend output files will now be named as output_tag<N>_<tosa_spec>.tosa instead of output_tag.tosa.

cc @digantdesai @freddan80 @per @zingo

Copy link

pytorch-bot bot commented Mar 19, 2025

🔗 Helpful Links

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

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

❌ 4 New Failures

As of commit fa1e3bb with merge base 644b7dd (image):

NEW FAILURES - The following jobs have failed:

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

@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 Mar 19, 2025
@oscarandersson8218 oscarandersson8218 added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk topic: not user facing labels Mar 19, 2025
@zingo
Copy link
Collaborator

zingo commented Mar 19, 2025

Hi @larryliu0820

This broke our internal tests and we need to revert it first. Could you please re-submit the PR, and wait for us to import and run internal CI, and paste the error message?

Hi could you help us point out what error you got from this, to help us knowing how to avoid this better in the future or even better could the internal tests be ported to be runned in github also so we can get proper testing while merging?

@facebook-github-bot
Copy link
Contributor

@larryliu0820 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@larryliu0820
Copy link
Contributor

Hi @larryliu0820

This broke our internal tests and we need to revert it first. Could you please re-submit the PR, and wait for us to import and run internal CI, and paste the error message?

Hi could you help us point out what error you got from this, to help us knowing how to avoid this better in the future or even better could the internal tests be ported to be runned in github also so we can get proper testing while merging?

The original PR was failing all executorch/backends/arm/test tests internally. Haven't looked into the details of the tests and also not sure why it's not showing up in OSS CI. I reimported this retry PR and see if it passes this time.

@zingo
Copy link
Collaborator

zingo commented Mar 19, 2025

This patch renames the tosa files could you have tests that assume some filenames?

@larryliu0820
Copy link
Contributor

This seems fine in terms of internal test

@zingo
Copy link
Collaborator

zingo commented Mar 20, 2025

Hi @larryliu0820 does this mean we should go ahead and merge this again now? Or will you merge it to do the extended testing?

@@ -122,10 +123,12 @@ def preprocess( # noqa: C901

if artifact_path:
tag = _get_first_delegation_tag(graph_module)
et_version = version("executorch")
Copy link
Contributor

Choose a reason for hiding this comment

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

This is causing issues for internal setup, I need to take a look.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks, This was merged and reverted during your days off and we were asked to reupload the PR. We don't know what caused the problem so the PR was unchanged. One suspicion we have is if you assume and tosa file names in some way in your flow that would break as they get renamed by this patch.

Copy link
Contributor

Choose a reason for hiding this comment

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

I need to take a better look at internal failures but this could be because of how packages are set up internally. Can we drop et_version for now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, that's fine for us.

@oscarandersson8218
Copy link
Collaborator Author

I messed up the rebase a bit, hence all the added reviewers in the log. Sorry about that. PR should be in a good state again though.

@zingo zingo changed the title Arm backend: Add tosa_spec and et-version info to .tosa files Arm backend: Add tosa_spec info to .tosa files Mar 21, 2025
@digantdesai
Copy link
Contributor

LGTM, stamped. Let me pull internally just to be safe (re-revert would be bad :p) - should take a couple of hours. I can merge it if you don't mind.

@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@zingo
Copy link
Collaborator

zingo commented Mar 21, 2025

Thanks, please go ahead 🙏

@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@digantdesai
Copy link
Contributor

Ci failures related? Internal CI is happy.

@oscarandersson8218
Copy link
Collaborator Author

Ci failures related? Internal CI is happy.

@digantdesai Don't think they are related. trunk/test-arm-reference-delegation/linux-job should be fixed by #9641

@zingo zingo merged commit 07266f9 into pytorch:main Mar 27, 2025
162 of 166 checks passed
kirklandsign pushed a commit that referenced this pull request Apr 11, 2025
Arm backend output files will now be named as
`output_tag<N>_<tosa_spec>.tosa` instead of `output_tag.tosa`.

Signed-off-by: Oscar Andersson <[email protected]>
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