-
Notifications
You must be signed in to change notification settings - Fork 684
Dissable EDSR benchmarking #13877
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
Dissable EDSR benchmarking #13877
Conversation
QNN doesn't support that
🔗 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 SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 3 New Failures, 1 Unrelated FailureAs of commit d560633 with merge base e38c077 ( 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. |
This PR needs a
|
@kirklandsign are those android-perf failures related? |
I think we test |
@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? |
@haowhsu-quic Seems that android-perf / build-benchmark-app / linux-job (pull_request) is a new failure |
And the log is
Is it related to 2.37 uprev? |
I think that is the root cause. |
This indicates the QNN_SDK_ROOT was not setup properly. |
Exporting the model continues to fail now.