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.

Sign up for GitHub

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

Jump to bottom

Test failure: System.Diagnostics.Tests.ProcessTests.TestGetProcessById #107821

Open
v-wenyuxu opened this issue Sep 14, 2024 · 2 comments
Open

Test failure: System.Diagnostics.Tests.ProcessTests.TestGetProcessById #107821

v-wenyuxu opened this issue Sep 14, 2024 · 2 comments
Labels
arch-x64 area-System.Diagnostics.Process blocking-clean-ci-optional Blocking optional rolling runs help wanted [up-for-grabs] Good issue for external contributors JitStress CLR JIT issues involving JIT internal stress modes os-linux Linux OS (any supported distro) test-bug Problem in test source code (most likely)
Milestone
Future

Comments

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-jitstress 20240913.1

Failed tests:

net9.0-linux-Release-x64-jitstress2-Ubuntu.2204.Amd64.Open
    - System.Diagnostics.Tests.ProcessTests.TestGetProcessById

Error message:

 Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: ".NET Long Runni"
Actual:   "dotnet"
           ↑ (pos 0)

Stack trace:

   at System.Diagnostics.Tests.ProcessTests.TestGetProcessById() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs:line 1177
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
@v-wenyuxu v-wenyuxu added os-linux Linux OS (any supported distro) JitStress CLR JIT issues involving JIT internal stress modes arch-x64 blocking-clean-ci-optional Blocking optional rolling runs labels Sep 14, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Sep 14, 2024
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

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

@jeffhandley jeffhandley added test-bug Problem in test source code (most likely) help wanted [up-for-grabs] Good issue for external contributors and removed untriaged New issue has not been triaged by the area owner labels Sep 17, 2024
@jeffhandley jeffhandley added this to the Future milestone Sep 17, 2024
@v-wenyuxu
Copy link
Author

Failed in: runtime-coreclr libraries-jitstress 20240917.1

Failed tests:

net9.0-linux-Release-x64-jitstress2-Ubuntu.2204.Amd64.Open
    - System.Diagnostics.Tests.ProcessTests.TestGetProcessById

Error message:

 Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: ".NET Long Runni"
Actual:   "dotnet"
           ↑ (pos 0)

Stack trace:

   at System.Diagnostics.Tests.ProcessTests.TestGetProcessById() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessTests.cs:line 1177
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57

@mdh1418 mdh1418 mentioned this issue Dec 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-x64 area-System.Diagnostics.Process blocking-clean-ci-optional Blocking optional rolling runs help wanted [up-for-grabs] Good issue for external contributors JitStress CLR JIT issues involving JIT internal stress modes os-linux Linux OS (any supported distro) test-bug Problem in test source code (most likely)
Projects
None yet
Milestone
Future
Development

No branches or pull requests
2 participants
@jeffhandley @v-wenyuxu