-
Notifications
You must be signed in to change notification settings - Fork 949
refreshenv.cmd uses hard-coded temp files #1986
Copy link
Copy link
Open
Labels
0 - TriagingIssue is accepted, but a milestone has yet to be added for the issue.Issue is accepted, but a milestone has yet to be added for the issue.BugIssues where something has happened which was not expected or intended.Issues where something has happened which was not expected or intended.
Metadata
Metadata
Assignees
Labels
0 - TriagingIssue is accepted, but a milestone has yet to be added for the issue.Issue is accepted, but a milestone has yet to be added for the issue.BugIssues where something has happened which was not expected or intended.Issues where something has happened which was not expected or intended.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What You Are Seeing?
When running refreshenv at the same time under multiple command prompt windows it tries to write _envset.tmp and _env.cmd but ends up in a race condition situation as the files are locked by other process. This is not an issue when running refreshenv manually but when automating things and optimizing the automation by parallelism.
What is Expected?
The temp files should be written with random file names.
How Did You Get This To Happen? (Steps to Reproduce)
Write a script which launches multiple command prompts and runs refreshenv on each.
Output Log