Repository navigation
Fix Windows QDK integration test paths and add Windows CI - #19
Merged
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.
The real QDK factory test failed on Windows when hash-partitioned paths exceeded the legacy path limit, even with a short pytest base directory. Use extended absolute temporary paths on Windows, document the same data-root requirement for consumers, and add a Windows full-suite job without renaming the existing Linux required checks.
Validation: all 176 tests passed on Windows/Python 3.12, including the previously failing real QDK test; branch-inclusive coverage 88.64%; Ruff check and format passed. Existing locked dependencies and frozen fixtures are unchanged.