-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.Diagnostics.Tests.ProcessModuleTests.ModulesAreDisposedWhenProcessIsDisposed test is failing #68035
Comments
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process Issue DetailsConfiguration:
|
runtime/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/ProcessManager.Win32.cs Lines 226 to 230 in 599f0bc
here's a little more context from the .NET Framework code:
Options - increase the 50 to 100 (it's a failure mode anyway); or change ModulesAreDisposedWhenProcessIsDisposed to retry. |
In the last 2 months, this has failed 2x , both Windows 7 x86, but of none of the other tests that get Is there an issue with the process not fully starting? There is a 50ms loop above, but perhaps not always enough. Looking back in history, there was an attempt presumably this issue with a spin wait in such a test. But when it failed with this error, it was replaced with a test using the current process. With this evidence, a change to the product seems like a hack. I will just add a retry on this test. |
Build: https://dnceng.visualstudio.com/public/_build/results?buildId=1711437&view=ms.vss-test-web.build-test-results-tab&runId=46535502&resultId=129201&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
Configuration:
net7.0-windows-Release-x86-CoreCLR_release-Windows.7.Amd64.Open
The text was updated successfully, but these errors were encountered: