fix(sysinfo): raise on EP-not-available-on-system#686
Merged
Conversation
added 2 commits
May 20, 2026 17:15
xieofxie
changed the title
added 2 commits
May 21, 2026 10:28
timenick
approved these changes
May 21, 2026
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
2 participants
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
resolve_deviceraises when the requested EP is known but not actually present on the current system (e.g.--ep vitisaion a non-Vitis machine), replacing the previous silent warn-and-fall-back-to-CPU behavior that produced unusable configs.tests/unit/sysinfo/test_device.pyto cover the new raise paths.This follows how we raise when no ep found for a device, it fixes when the device is auto. i.e. now if device = auto and ep = a not supported one, we will raise
Closes #634