-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.ComponentModel.Win32Exception : An error occurred trying to start process 'notepad.exe' with working directory 'C:\h\w\9F8D0903\w\B7E309C0\e'. Access is denied #90406
Comments
@Maoni0 It looks like this error is impacting Runtime only. Is this an infra failure or a failure specific to Runtime tests? |
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process Issue DetailsBuildhttps://dev.azure.com/dnceng-public/public/_build/results?buildId=302756&view=results
Build leg reportedSystem.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_NotepadWithContent_withArgumentList Pull RequestKnown issue core informationFill out the known issue JSON section by following the step by step documentation on how to create a known issue {
"ErrorMessage" : "",
"BuildRetry": false,
"ErrorPattern": "System.ComponentModel.Win32Exception : An error occurred trying to start process .* with working directory",
"ExcludeConsoleLog": false
} @dotnet/dnceng Release Note Category
Release Note DescriptionAdditional information about the issue reportedNo response ReportSummary
Known issue validationBuild: 🔎
|
Added this to the 9.0.0 milestone because of the frequency |
Triage:
StartInfo_NotepadWithContent_withArgumentListStartInfo_NotepadWithContent_withArgumentList is not the only S.D.P test that starts notepad, but it's the only one that fails. The difference is that it uses a different property to set the arguments: runtime/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs Line 1337 in 80ffac5
runtime/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs Line 1101 in 80ffac5
But both properties are later mapped to a string: runtime/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Win32.cs Line 50 in 87a32e7
and the same sys-call is being performed: So in theory, both should be equally stable. When searching for runtime/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Win32.cs Lines 169 to 183 in 87a32e7
It's going to require further triage. |
We can defer this out of 9.0.0. It does have a notable hit count, but it's not new. I moved it to Future. |
Build
https://dev.azure.com/dnceng-public/public/_build/results?buildId=302756&view=results
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-87372-merge-563116f2d3404bad82/System.Diagnostics.Process.Tests/1/console.b1eb782a.log?helixlogtype=result
Build leg reported
System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_NotepadWithContent_withArgumentList
Pull Request
#87372
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Report
Summary
Known issue validation
Build: 🔎⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line.
Result validation:
Validation performed at: 8/11/2023 4:35:48 PM UTC
The text was updated successfully, but these errors were encountered: