Reset the working directory of child processes we spawn on Windows. #1212
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
grynspan
requested review from
stmontgomery,
briancroom and
suzannaratcliff
as code owners
grynspan
added
bug
|
@swift-ci test |
|
@swift-ci test Linux |
|
@swift-ci test |
1 similar comment
|
@swift-ci test |
|
I'm not planning to apply the same change to the |
jmschonfeld
approved these changes
Jul 8, 2025
There was a problem hiding this comment.
Seems fine to me. Agreed that making a similar change to the posix spawn path seems like a good idea. The temporary directory might also be a good CWD to use instead of the root directory if it's easier to get to / works better but the root directory seems fine too given that exit tests likely shouldn't rely on the CWD
compnerd
reviewed
Jul 8, 2025
|
@swift-ci test |
stmontgomery
approved these changes
Jul 8, 2025
|
@swift-ci test |
briancroom
approved these changes
Jul 8, 2025
|
@swift-ci test |
1 similar comment
|
@swift-ci test |
|
@swift-ci test Windows |
This PR modifies the Windows implementation of `spawnProcess()` so that it sets the working directory of the new process to "C:\" (or thereabouts). This prevents a race condition on Windows because that system won't let you delete a directory if it's the working directory of any process. See [The Old New Thing](https://devblogs.microsoft.com/oldnewthing/20101109-00/?p=12323) for a very on-the-nose blog post. Note that we do not specify the value of the working directory in an exit test body. A test should generally not rely on it anyway because it is global state and any thread could change its value at any time. I haven't written a unit test for this change because it's unclear what I could write that would be easily verifiable, and because I don't know what state I might perturb outside such a test by calling `SetCurrentDirectory()`. Resolves #1209. (This is a speculative fix.)
grynspan
force-pushed
the
jgrynspan/1209-working-directories-are-terrible
branch
from
1dea725 to
7cb5040
Compare
|
@swift-ci test |
|
@swift-ci test Linux |
|
@swift-ci test macOS |
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.
This PR modifies the Windows implementation of
spawnProcess()so that it sets the working directory of the new process to "C:" (or thereabouts). This prevents a race condition on Windows because that system won't let you delete a directory if it's the working directory of any process. See The Old New Thing for a very on-the-nose blog post.Note that we do not specify the value of the working directory in an exit test body. A test should generally not rely on it anyway because it is global state and any thread could change its value at any time.
I haven't written a unit test for this change because it's unclear what I could write that would be easily verifiable, and because I don't know what state I might perturb outside such a test by calling
SetCurrentDirectory().Resolves #1209.
(This is a speculative fix.)
Checklist: