-
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
Test failure: System.Diagnostics.Tests.ProcessTests.ProcessStart_OnLinux_UsesSpecifiedProgramUsingArgumentList #109630
Comments
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process |
Failed in: runtime-coreclr libraries-jitstress 20241122.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress 20241125.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr libraries-jitstress-random 20241228.1 Failed tests:
Error message:
Stack trace:
|
Assigned to @adamsitnik for triage |
Triage: it seems that reading a process name on Linux makes some of our tests flaky (#109630, #110643, #111460). @jkotas has suggested in #111460 (comment) that we maybe reading it too soon. I am going to try to add a simple retry mechanism to see if it helps. |
Failed in: runtime-coreclr libraries-jitstress 20241106.1
Failed tests:
Error message:
Stack trace:
The text was updated successfully, but these errors were encountered: