Enable QNN unit tests on Windows ARM64 internal-symbol builds - #838
Draft
tzuhsuanwei wants to merge 3 commits into
Draft
tzuhsuanwei wants to merge 3 commits into
tzuhsuanwei wants to merge 3 commits into
Conversation
tzuhsuanwei
changed the base branch from
dev/yuhuchua/migrate-clip-ut
to
main
September 16, 2026 07:47
tzuhsuanwei
force-pushed
the
dev/tzuhwei/windows-arm64-qnn-ut-internal-symbols
branch
4 times, most recently
from
September 16, 2026 08:37
1cc5c29 to
4f43059
Compare
tzuhsuanwei
changed the base branch from
main
to
dev/yuhuchua/windows-qnn-ut-internal-symbols
September 16, 2026 08:37
tzuhsuanwei
force-pushed
the
dev/tzuhwei/windows-arm64-qnn-ut-internal-symbols
branch
5 times, most recently
from
September 17, 2026 09:37
c0049d4 to
1f38553
Compare
yuhuchua-qti
force-pushed
the
dev/yuhuchua/windows-qnn-ut-internal-symbols
branch
from
September 23, 2026 04:17
de0bfab to
160e747
Compare
tzuhsuanwei
force-pushed
the
dev/tzuhwei/windows-arm64-qnn-ut-internal-symbols
branch
3 times, most recently
from
September 23, 2026 09:45
53fd2b1 to
c5ab998
Compare
yuhuchua-qti
force-pushed
the
dev/yuhuchua/windows-qnn-ut-internal-symbols
branch
from
September 24, 2026 10:07
160e747 to
8648fff
Compare
tzuhsuanwei
force-pushed
the
dev/tzuhwei/windows-arm64-qnn-ut-internal-symbols
branch
from
September 29, 2026 09:49
c5ab998 to
4cf8c83
Compare
This branch has not been deployed
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
Enable the QNN internal-symbol unit-test build on Windows ARM64.
This stacks on #831 and adds the ARM64 build path plus a Draft-PR workflow: build on an x64 Windows builder, then run the QNN unit suite on a Windows ARM64 test runner.
CI scope
QnnUnit_*component/unit suiteWindows ARM64 test coverage
The original ARM64 CI result was 861 tests: 858 passed, 3 skipped. After the changes below, the pre-rebase Windows ARM64 CI result was 863 tests: 861 passed, 2 skipped.
SetupBackend_HTP_WithHtpArch_ReportsPlatformArchV73assertion on x86, where the HTP emulator reports the configured arch.GetHtpArch()returns a discovered physical HTP arch (!= NONE) instead of assumingV73.ValidateCompatibilityInfo_MalformedOnArm64_LogsDeserializationFailureAndReturnsNotApplicableEP_NOT_APPLICABLE, rather than taking the x86 platform-skip path.HTP host device discovery
GetSupportedDevices_HtpHost_CreatesEpDevicefor ARM64, verifying that a Qualcomm NPU/HTP host device creates an EP device.Rebase, Accuracy, and Snapshot validation
This branch includes the #831 Phase 3 tier infrastructure (
160e747423), which enablesQNN_EP_ACCURACY_UTfor internal-symbol builds.The supplied-golden validation (run 36551637367) passed:
QnnUnit_Clip_AccuracyTest(7),QnnUnit_Clip_Accuracy_QDQFloatTest(5),QnnUnit_Clip_Accuracy_QDQQuantTest(4), andQnnUnit_Clip_Accuracy_FoldedConstTest(2).QNN_SNAPSHOT_DRIFT; none wereQNN_GOLDEN_ABSENT.The supplied golden was produced from a different source baseline, so this result validates the drift-to-Accuracy route rather than snapshot equality. A Windows ARM64 golden generated from the matching source/config is required before the 18 snapshot comparisons can be expected to match exactly.