Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Test failure: System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents #112621

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

Open
v-wenyuxu opened this issue Feb 17, 2025 · 6 comments
Labels
arch-arm64 area-System.Diagnostics.Tracing blocking-clean-ci-optional Blocking optional rolling runs os-linux Linux OS (any supported distro)
Milestone

Comments

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-pgo 20250216.1

Failed tests:

net10.0-linux-Release-arm64-jitosr_stress-(Ubuntu.2404.Arm64.Open)[email protected]/dotnet-buildtools/prereqs:ubuntu-24.04-helix-arm64v8
    - System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents
net10.0-linux-Release-x64-jitosr_stress-Ubuntu.2204.Amd64.Open
    - System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents
net10.0-windows-Release-x64-jitosr_stress-Windows.10.Amd64.Open
    - System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents

Error message:

 Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 134 but it should have been 42

Stack trace:

   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose() in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 55
   at System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents() in /_/src/libraries/System.Diagnostics.DiagnosticSource/tests/DiagnosticSourceEventSourceBridgeTests.cs:line 38
   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.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
   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 arch-arm64 blocking-clean-ci-optional Blocking optional rolling runs os-linux Linux OS (any supported distro) labels Feb 17, 2025
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Feb 17, 2025
Copy link
Contributor

Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti
See info in area-owners.md if you want to be subscribed.

@tarekgh tarekgh added this to the Future milestone Feb 17, 2025
@tarekgh tarekgh removed the untriaged New issue has not been triaged by the area owner label Feb 17, 2025
@tarekgh
Copy link
Member

tarekgh commented Feb 17, 2025

Most likely this is a time out in the remote executor. Increasing the remote executor timeout in the test should help.

@SakeTao
Copy link

SakeTao commented Apr 21, 2025

Failed in: runtime-coreclr libraries-pgo 20250420.1

Failed tests:

net10.0-windows-Release-x86-jitosr_stress_random-Windows.10.Amd64.Open
    - System.Reflection.Metadata.ApplyUpdateTest.TestGenericAddStaticField

Error message:

 Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was -1073740286 but it should have been 42

Stack trace:

   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242
   at System.Reflection.Metadata.ApplyUpdateUtil.TestCase(Action testBody, RemoteInvokeOptions options) in /_/src/libraries/System.Runtime.Loader/tests/ApplyUpdateUtil.cs:line 130
   at System.Reflection.Metadata.ApplyUpdateTest.TestGenericAddStaticField() in /_/src/libraries/System.Runtime.Loader/tests/ApplyUpdateTest.cs:line 896
   at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.cs:line 126

@tarekgh
Copy link
Member

tarekgh commented Apr 21, 2025

@SakeTao this is a different failure than the one reported in this issue. You may open a new issue track the new one under System.Reflection.Metadat area.

@SakeTao
Copy link

SakeTao commented May 6, 2025

Failed in: runtime-coreclr libraries-jitstress-random 20250503.1

Failed tests:

net10.0-windows-Release-x86-jitstress_random_2-Windows.10.Amd64.Open
    - System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents

Error message:

 Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was -1073740286 but it should have been 42

Stack trace:

   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/arcade/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose() in /_/src/arcade/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 55
   at System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestEnableAllActivitySourcesAllEvents() in /_/src/libraries/System.Diagnostics.DiagnosticSource/tests/DiagnosticSourceEventSourceBridgeTests.cs:line 39
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57

@tarekgh
Copy link
Member

tarekgh commented May 6, 2025

@SakeTao are you interested in submitting a PR to fix this issue? I think we just need to increase the timeout to the remote executor for the failing test, something like the following:

}, new RemoteInvokeOptions() { TimeOut = 30_000, ExpectedExitCode = expectedExitCode }); // give a 30 second time out, so if this does hang, it doesn't hang for the full timeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-arm64 area-System.Diagnostics.Tracing blocking-clean-ci-optional Blocking optional rolling runs os-linux Linux OS (any supported distro)
Projects
None yet
Development

No branches or pull requests

3 participants