Test failure: System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

[v-wenyuxu]

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "[FAIL] System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Failed in: runtime-coreclr crossgen2 20240710.1

Failed tests:

net9.0-windows-Release-x64-TestReadyToRun_Release-(Windows.Nano.1809.Amd64.Open)windows.10.amd64.serverrs5.open@mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64
    - System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

Error message:

 Assert.Equal() Failure: Values differ
Expected: 0
Actual:   298

Stack trace:

   at System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(Boolean useShellExecute) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs:line 1276
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=736959
Error message validated: [[FAIL] System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/15/2024 10:03:05 AM UTC

Report

Build	Definition	Test	Pull Request
741969	dotnet/runtime	System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)	#104904
736959	dotnet/runtime	System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	2	2

[danmoseley]

ERROR_TOO_MANY_POSTS
298 (0x12A)
Too many posts were made to a semaphore.

...?

[v-wenyuxu]

Failed in: runtime-coreclr crossgen2 20240713.1

Failed tests:

net9.0-windows-Release-x64-TestReadyToRun_Release-(Windows.Nano.1809.Amd64.Open)windows.10.amd64.serverrs5.open@mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64
    - System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

Error message:

 Assert.Equal() Failure: Values differ
Expected: 0
Actual:   298

Stack trace:

   at System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(Boolean useShellExecute) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs:line 1276
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

[v-wenyuxu]

Failed in: runtime-coreclr crossgen2 20240714.1

Failed tests:

net9.0-windows-Release-x64-TestReadyToRun_Release-(Windows.Nano.1809.Amd64.Open)windows.10.amd64.serverrs5.open@mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64
    - System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

Error message:

 Assert.Equal() Failure: Values differ
Expected: 0
Actual:   298

Stack trace:

   at System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(Boolean useShellExecute) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs:line 1276
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

[mangod9]

@JulieLeeMSFT, this doesnt look like an R2R related issue. Any reason its assigned to me? Anyways @steveisok now owns R2R.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.

[MichalStrehovsky]

@JulieLeeMSFT, this doesnt look like an R2R related issue. Any reason its assigned to me? Anyways @steveisok now owns R2R.

This is not R2R, we're also seeing it in native AOT legs. I'm closing the native AOT flavor of this bug as a dup of this one.

[MichalStrehovsky]

The common theme between the R2R and native AOT failures seems to be Windows Nano Server.

[JulieLeeMSFT]

@MichalStrehovsky, thanks for triaging.
Removed assignment to @mangod9.

[v-wenyuxu]

Failed in: runtime-coreclr crossgen2 20240715.2

Failed tests:

net9.0-windows-Release-x64-TestReadyToRun_Release-(Windows.Nano.1809.Amd64.Open)windows.10.amd64.serverrs5.open@mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64
    - System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(useShellExecute: False)

Error message:

 Assert.Equal() Failure: Values differ
Expected: 0
Actual:   298

Stack trace:

   at System.Diagnostics.Tests.ProcessStartInfoTests.StartInfo_BadExe(Boolean useShellExecute) in /_/src/libraries/System.Diagnostics.Process/tests/ProcessStartInfoTests.cs:line 1276
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)