Skip to content
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/LongProcessNamesAreSupported #29383

Open
AriNuer opened this issue Apr 26, 2019 · 6 comments
Assignees
Labels
area-System.Diagnostics.Process blocking-clean-ci-optional Blocking optional rolling runs Known Build Error Use this to report build issues in the .NET Helix tab test-run-core Test failures in .NET Core test runs
Milestone

Comments

@AriNuer
Copy link

AriNuer commented Apr 26, 2019

Test System.Diagnostics.Tests.ProcessTests/LongProcessNamesAreSupported has failed.

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=973726
Build error leg or test failing: System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
Pull request: #89196

Error Message

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

Message :

Assert.Contains() Failure
Not found: (filter expression)
In value:  Process[] [System.Diagnostics.Process (sh), System.Diagnostics.Process (sh), System.Diagnostics.Process (bash), System.Diagnostics.Process (dotnet)]

Stack Trace :

at System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported() in /__w/1/s/src/System.Diagnostics.Process/tests/ProcessTests.cs:line 1883

Details:
https://mc.dot.net/#/product/netcore/30/source/official~2Fdotnet~2Fcorefx~2Frefs~2Fheads~2Fmaster/type/test~2Ffunctional~2Fcli~2F/build/20190425.7/workItem/System.Diagnostics.Process.Tests/analysis/xunit/System.Diagnostics.Tests.ProcessTests~2FLongProcessNamesAreSupported

Known issue validation

Build: 🔎
Result validation: ⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line.
Validation performed at: 3/10/2025 10:46:51 PM UTC

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=973726
Error message validated: [[FAIL] System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/10/2025 10:56:44 PM UTC

Report

Build Definition Test Pull Request
989141 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
985334 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
984914 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
983587 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
982500 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported #113598
983281 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported #113602
982680 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
982187 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
982047 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
981826 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
981548 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
981041 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
980252 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported
973726 dotnet/runtime System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported #113214

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 14
@wtgodbe
Copy link
Member

wtgodbe commented May 2, 2019

@wtgodbe wtgodbe closed this as completed May 2, 2019
@msftgits msftgits transferred this issue from dotnet/corefx Feb 1, 2020
@msftgits msftgits added this to the 3.0 milestone Feb 1, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 13, 2020
@Anipik Anipik reopened this Feb 8, 2021
@Anipik
Copy link
Contributor

Anipik commented Feb 8, 2021

Failed again here https://dev.azure.com/dnceng/public/_build/results?buildId=982443&view=logs&j=b9b7de4d-2126-5581-6453-1576f9aaac5f&t=db048d48-40e8-5399-9b14-d587763f33ff

log https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-master-f42ca9b897964959b9/System.Diagnostics.Process.Tests/console.006564c7.log?sv=2019-07-07&se=2021-02-27T14%3A16%3A51Z&sr=c&sp=rl&sig=NdWxmCLpMC65XXifBPdBuJjlZWau5zODq1eSLz3DZNQ%3D

  Discovering: System.Diagnostics.Process.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Diagnostics.Process.Tests (found 246 of 304 test cases)
  Starting:    System.Diagnostics.Process.Tests (parallel test collections = on, max threads = 2)
    System.Diagnostics.Tests.ProcessStartInfoTests.ShellExecute_Nano_Fails_Start [SKIP]
      Condition(s) not met: "IsWindowsNanoServer"
Linux
Linux
Linux
Linux
None of the following programs were installed on this machine: xdg-open,gnome-open,kfmclient.
    System.Diagnostics.Tests.ProcessTests.TestProcessRecycledPid [SKIP]
      Condition(s) not met: "IsStressModeEnabledAndRemoteExecutorSupported"
    System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported [FAIL]
      Assert.Contains() Failure
      Not found: (filter expression)
      In value:  Process[] [System.Diagnostics.Process (helix_docker_work.sh), System.Diagnostics.Process (execute.sh), System.Diagnostics.Process (bash), System.Diagnostics.Process (dotnet), System.Diagnostics.Process (123456789012345)]
      Stack Trace:
        /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs(2067,0): at System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported()
  Finished:    System.Diagnostics.Process.Tests
=== TEST EXECUTION SUMMARY ===
   System.Diagnostics.Process.Tests  Total: 307, Errors: 0, Failed: 1, Skipped: 2, Time: 10.385s
/root/helix/work/workitem

@akoeplinger akoeplinger modified the milestones: 3.0, Future Mar 25, 2021
@ericstj
Copy link
Member

ericstj commented Jul 19, 2023

Failed again in #89196

    System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported [FAIL]
      Assert.Contains() Failure
      Not found: (filter expression)
      In value:  Process[] [System.Diagnostics.Process (helix_docker_work.sh), System.Diagnostics.Process (execute.sh), System.Diagnostics.Process (bash), System.Diagnostics.Process (dotnet), System.Diagnostics.Process (123456789012345)]
      Stack Trace:
        /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs(2298,0): at System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported()
        /_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs(22,0): at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
        /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs(57,0): at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

@ericstj
Copy link
Member

ericstj commented Jul 19, 2023

Relevant test case:
https://github.com/dotnet/runtime/blob/50ba405797f6cc57d57ff4d2503079b4c32acc7b/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs#L2289C45-L2298

Seems to me like that last process is the one, but it's name was truncated:
System.Diagnostics.Process (123456789012345)

@dotnet dotnet unlocked this conversation Nov 24, 2023
@JulieLeeMSFT
Copy link
Member

Failed again in runtime-coreclr libraries-jitstress/20241211.2

  Discovering: System.Diagnostics.Process.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Diagnostics.Process.Tests (found 262 of 324 test cases)
  Starting:    System.Diagnostics.Process.Tests (parallel test collections = on [2 threads], stop on fail = off)
    System.Diagnostics.Tests.ProcessStartInfoTests.ShellExecute_Nano_Fails_Start [SKIP]
      Condition(s) not met: "IsWindowsNanoServer"
Linux
Linux
Linux
Linux
    System.Diagnostics.Tests.ProcessTests.TestBasePriorityOnUnix [SKIP]
      Condition(s) not met: "IsPrivilegedProcess"
None of the following programs were installed on this machine: xdg-open,gnome-open,kfmclient.
    System.Diagnostics.Tests.ProcessTests.TestPriorityClassUnix [SKIP]
      Condition(s) not met: "IsPrivilegedProcess"
    System.Diagnostics.Tests.ProcessTests.TestProcessRecycledPid [SKIP]
      Condition(s) not met: "IsStressModeEnabledAndRemoteExecutorSupported"
    System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported [FAIL]
      Assert.Contains() Failure: Filter not matched in collection
      Collection: [System.Diagnostics.Process (helix_docker_work.sh), System.Diagnostics.Process (execute.sh), System.Diagnostics.Process (bash), System.Diagnostics.Process (dotnet), System.Diagnostics.Process (123456789012345)]
      Stack Trace:
        /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs(2300,0): at System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported()

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-jitstress 20241211.2

Failed tests:

net10.0-linux-Release-arm-jitstress1_tiered-(Debian.12.Arm32.Open)Ubuntu.2204.ArmArch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-12-helix-arm32v7
    - System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported

Error message:

 Assert.Contains() Failure: Filter not matched in collection
Collection: [System.Diagnostics.Process (helix_docker_work.sh), System.Diagnostics.Process (execute.sh), System.Diagnostics.Process (bash), System.Diagnostics.Process (dotnet), System.Diagnostics.Process (123456789012345)]

Stack trace:

   at System.Diagnostics.Tests.ProcessTests.LongProcessNamesAreSupported() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs:line 2300
   at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
   at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor) in /_/src/coreclr/System.Private.CoreLib/src/System/RuntimeHandles.cs:line 1128
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 48

@MichalStrehovsky MichalStrehovsky added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab blocking-clean-ci-optional Blocking optional rolling runs and removed blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' labels Mar 10, 2025
MichalStrehovsky added a commit that referenced this issue Mar 14, 2025
We don't collect stats on these pipelines so the hit count on issues like #29383 don't get updated with hits in nativeaot runs.

At this point `runtime-nativeaot-outerloop` is more reliable than e.g. `runtime-libraries-coreclr outerloop` that hasn't seen a successful run in years.
MichalStrehovsky added a commit that referenced this issue Mar 14, 2025
We don't collect stats on these pipelines so the hit count on issues like #29383 don't get updated with hits in nativeaot runs.

At this point `runtime-nativeaot-outerloop` is more reliable than e.g. `runtime-libraries-coreclr outerloop` that hasn't seen a successful run in years.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Diagnostics.Process blocking-clean-ci-optional Blocking optional rolling runs Known Build Error Use this to report build issues in the .NET Helix tab test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

No branches or pull requests

10 participants