Revalidate the current ONNX model on Qualcomm QNN - #49
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Physical-device results
Source ONNX SHA-256:
191927e05b5f82a539f0ad35c78dafe7f969cb4e57e9c76556cb9f35053e658eCompile jobs:
jpyxnmd05,jp0jk610g,jp8x813qgLink job:
jgk4d8lvpProfile jobs:
j567vw3np,jpyxnmvr5,jglx7lllgInference jobs:
jg9m8d3q5,jpez2yl7p,jgk4d82opVerification
ruff format --check .ruff check .The full local pytest collection was blocked by a stale macOS scikit-learn binary in the existing virtual environment; GitHub's clean Linux CI remains the authoritative full-suite run.
Power remains unmeasured, and AI Hub model-profile latency is not presented as Android application end-to-end latency.