Skip to content

Conversation

kirklandsign
Copy link
Contributor

@kirklandsign kirklandsign commented Sep 2, 2025

Exporting the model continues to fail now.

QNN doesn't support that
Copy link

pytorch-bot bot commented Sep 2, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 3 New Failures, 1 Unrelated Failure

As of commit d560633 with merge base e38c077 (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@meta-cla meta-cla 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 Sep 2, 2025
@kirklandsign kirklandsign marked this pull request as ready for review September 2, 2025 18:15
Copy link

github-actions bot commented Sep 2, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@kirklandsign kirklandsign temporarily deployed to upload-benchmark-results September 2, 2025 18:36 — with GitHub Actions Inactive
@cccclai
Copy link
Contributor

cccclai commented Sep 2, 2025

@shoumikhin
Copy link
Contributor

@kirklandsign are those android-perf failures related?

@haowhsu-quic
Copy link
Collaborator

I think we test edsr regularly in our CI, may I know the error you encountered?

@kirklandsign
Copy link
Contributor Author

@haowhsu-quic Sorry probably not related to QNN EDSR, but somehow this job won't run.

A separate issue, in https://github.com/pytorch/executorch/pull/13352/files#diff-f950d868ef7896638e2b7dea7d1a6c0dd0946861ecf12f8f6adf6077fb637c32R295, the version number is 2.37.0.25072. Should it be 2.37.0.250724?

@kirklandsign
Copy link
Contributor Author

@kirklandsign
Copy link
Contributor Author

And the log is

2025-09-03T20:15:34.4867374Z /pytorch/executorch/backends/qualcomm/runtime/backends/QnnFunctionInterface.h:10:10: fatal error: 'QnnInterface.h' file not found
2025-09-03T20:15:34.4868393Z    10 | #include "QnnInterface.h"
2025-09-03T20:15:34.4868769Z       |          ^~~~~~~~~~~~~~~~
2025-09-03T20:15:34.4869106Z 1 error generated.

Is it related to 2.37 uprev?

@kirklandsign kirklandsign merged commit 17cad55 into main Sep 3, 2025
119 of 125 checks passed
@kirklandsign kirklandsign deleted the edsr-benchmarking branch September 3, 2025 22:43
@haowhsu-quic
Copy link
Collaborator

@haowhsu-quic Sorry probably not related to QNN EDSR, but somehow this job won't run.

A separate issue, in https://github.com/pytorch/executorch/pull/13352/files#diff-f950d868ef7896638e2b7dea7d1a6c0dd0946861ecf12f8f6adf6077fb637c32R295, the version number is 2.37.0.25072. Should it be 2.37.0.250724?

I think that is the root cause.

@haowhsu-quic
Copy link
Collaborator

And the log is

2025-09-03T20:15:34.4867374Z /pytorch/executorch/backends/qualcomm/runtime/backends/QnnFunctionInterface.h:10:10: fatal error: 'QnnInterface.h' file not found
2025-09-03T20:15:34.4868393Z    10 | #include "QnnInterface.h"
2025-09-03T20:15:34.4868769Z       |          ^~~~~~~~~~~~~~~~
2025-09-03T20:15:34.4869106Z 1 error generated.

Is it related to 2.37 uprev?

This indicates the QNN_SDK_ROOT was not setup properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants