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

Re-enable calendars tests on NativeAOT/ARM32 #99595

Merged
merged 1 commit into from
Mar 12, 2024

Re-enable calendars tests on NativeAOT/ARM32

2d66549
Select commit
Loading
Failed to load commit list.
Merged

Re-enable calendars tests on NativeAOT/ARM32 #99595

Re-enable calendars tests on NativeAOT/ARM32
2d66549
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis failed Mar 12, 2024 in 0s

.NET Result Analysis

Details

⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis

Known test errors

Test Failures (2 tests failed)

🔹 [All failing tests from runtime]

    ❌ System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest [Console] [Details] [Artifacts] [0.04% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration
    Exception Message
    Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Half-way through waiting for remote process.
Timed out at 3/12/2024 11:47:56 AM after 60000ms waiting for remote process.
	Process ID: 1794
	Handle: 2406
	Name: dotnet
	MainModule: /datadisks/disk1/work/B0ED0956/p/dotnet
	StartTime: 3/12/2024 11:46:56 AM
	TotalProcessorTime: 00:00:01.0200000
    CallStack
       at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 225
   at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose() in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 55
   at System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest() in /_/src/libraries/System.Threading.ThreadPool/tests/ThreadPoolTests.cs:line 1038
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs:line 22
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
    ❌ System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest [Console] [Details] [Artifacts] [0.04% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration
    Exception Message
    Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 255 but it should have been 42
    CallStack
       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.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest() in /_/src/libraries/System.Threading.ThreadPool/tests/ThreadPoolTests.cs:line 1120
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs:line 22
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57

Was this helpful? Yes No

View more details on Build Analysis