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.PerformanceCounterTests.PerformanceCounter_IncrementBy_IncrementByReadOnly #105925

Open
v-wenyuxu opened this issue Aug 5, 2024 · 3 comments
Labels
arch-x64 area-System.Diagnostics.PerformanceCounter blocking-clean-ci-optional Blocking optional rolling runs JitStress CLR JIT issues involving JIT internal stress modes needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration os-windows
Milestone

Comments

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-jitstress2-jitstressregs 20240803.1

Failed tests:

net9.0-windows-Release-x64-jitstress2_jitstressregs0x1000-Windows.10.Amd64.Open
    - System.Diagnostics.Tests.PerformanceCounterTests.PerformanceCounter_IncrementBy_IncrementByReadOnly

Error message:

 System.ComponentModel.Win32Exception : The process cannot access the file because it is being used by another process.

Stack trace:

   at System.Diagnostics.PerformanceCounterLib.RegisterFiles(String arg0, Boolean unregister) in /_/src/libraries/System.Diagnostics.PerformanceCounter/src/System/Diagnostics/PerformanceCounterLib.cs:line 1233
   at System.Diagnostics.PerformanceCounterCategory.Delete(String categoryName) in /_/src/libraries/System.Diagnostics.PerformanceCounter/src/System/Diagnostics/PerformanceCounterCategory.cs:line 392
   at System.Diagnostics.Tests.Helpers.DeleteCategory(String categoryName) in /_/src/libraries/System.Diagnostics.PerformanceCounter/tests/Helpers.cs:line 56
   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-windows JitStress CLR JIT issues involving JIT internal stress modes arch-x64 blocking-clean-ci-optional Blocking optional rolling runs labels Aug 5, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Aug 5, 2024
Copy link
Contributor

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

@ericstj
Copy link
Member

ericstj commented Aug 5, 2024

https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-4276504538c24eecae/System.Diagnostics.PerformanceCounter.Tests/1/console.a3510fec.log?helixlogtype=result

C:\h\w\A4DA094B\w\AB5E093F\e>"C:\h\w\A4DA094B\p\dotnet.exe" exec --runtimeconfig System.Diagnostics.PerformanceCounter.Tests.runtimeconfig.json --depsfile System.Diagnostics.PerformanceCounter.Tests.deps.json xunit.console.dll System.Diagnostics.PerformanceCounter.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing  
  Discovering: System.Diagnostics.PerformanceCounter.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Diagnostics.PerformanceCounter.Tests (found 90 of 92 test cases)
  Starting:    System.Diagnostics.PerformanceCounter.Tests (parallel test collections = on [4 threads], stop on fail = off)
    System.Diagnostics.Tests.PerformanceCounterTests.PerformanceCounter_IncrementBy_IncrementByReadOnly [FAIL]
      System.ComponentModel.Win32Exception : The process cannot access the file because it is being used by another process.
      Stack Trace:
        /_/src/libraries/System.Diagnostics.PerformanceCounter/src/System/Diagnostics/PerformanceCounterLib.cs(1233,0): at System.Diagnostics.PerformanceCounterLib.RegisterFiles(String arg0, Boolean unregister)
        /_/src/libraries/System.Diagnostics.PerformanceCounter/src/System/Diagnostics/PerformanceCounterCategory.cs(392,0): at System.Diagnostics.PerformanceCounterCategory.Delete(String categoryName)
        /_/src/libraries/System.Diagnostics.PerformanceCounter/tests/Helpers.cs(56,0): at System.Diagnostics.Tests.Helpers.DeleteCategory(String categoryName)
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
        /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs(57,0): at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Info: Successfully installed performance counters in C:\h\w\A4DA094B\t\a1lrvxog.qbf\provider.man    System.Diagnostics.Tests.PerformanceDataTests.PerformanceCounter_PerformanceData [SKIP]
      Condition(s) not met: "IsRunnableEnvironment"

Info: Successfully uninstalled the performance counters from the counter definition XML file C:\h\w\A4DA094B\t\a1lrvxog.qbf\provider.man.  Finished:    System.Diagnostics.PerformanceCounter.Tests
=== TEST EXECUTION SUMMARY ===

Another one similar to #104572. Seems to me like we might have cross-talk between tests. I wonder if we should disable parallelization in these tests?

@ericstj ericstj added needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration and removed untriaged New issue has not been triaged by the area owner labels Aug 5, 2024
@ericstj ericstj added this to the Future milestone Aug 5, 2024
@mikelle-rogers
Copy link
Member

@ericstj, I noticed this test failure was put into future with no comments indicating the reason behind the milestone move, nor if the test was disabled. Would you please provide some clarity around that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-x64 area-System.Diagnostics.PerformanceCounter blocking-clean-ci-optional Blocking optional rolling runs JitStress CLR JIT issues involving JIT internal stress modes needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration os-windows
Projects
None yet
Development

No branches or pull requests

3 participants