[codex] Skip Windows symlink tests without permission#98
Closed
w287346141 wants to merge 1 commit into
Closed
Conversation
Author
|
Closing this PR to resubmit from the Star-Star66 account. |
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.
What changed
Why
The install-source test already handled Windows environments without Developer Mode or elevated symlink privileges, but the related install-prefix test still called symlinkSync directly. That made the full verification suite fail with EPERM even though the runtime behavior was not broken.
Impact
Windows contributors can run the full test suite without enabling symlink privileges. Environments that support symlinks still execute both regression tests normally.
Validation