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

[WASI] throw PNSE in ManualResetEventSlim.Wait #109839

Merged
merged 3 commits into from
Nov 19, 2024

unify

cc7a568
Select commit
Loading
Failed to load commit list.
Merged

[WASI] throw PNSE in ManualResetEventSlim.Wait #109839

unify
cc7a568
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Nov 19, 2024 in 0s

.NET Result Analysis

Details

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

All checks completed

[runtime-dev-innerloop]

[runtime]

Build Rerun

✔️ Build passed after 1 retries.

(Attempt #1) [link to build]

Build Rerun

✔️ Build passed after 1 retries.

(Attempt #1) [link to build]

runtime /

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]

runtime / Build / browser-wasm windows Release LibraryTests / Send to Helix

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌.packages\microsoft.dotnet.helix.sdk\10.0.0-beta.24556.2\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-ST-System.Net.Http.Functional.Tests in job 1030832c-0440-42bd-9bd1-ea7f652f609c has failed. [Failure log]

runtime / Build / Libraries Test Run checked coreclr linux_musl x64 Debug / Send to Helix

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.24556.2/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item LibraryImportGenerator.Tests in job edb76817-e249-4cfd-9ec8-0e6ca5083a0a has failed. [Failure log]

Non-Deterministic Test Failures Detected

LibraryImportGenerator.Tests.WorkItemExecution [Console] [Details] [Artifacts] [1.13% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]

Failing Configuration

System.Net.Http.Functional.Tests.HttpClientHandlerTest_Http1.SendAsync_HostHeader_First [Console] [Details] [Artifacts] [0.03% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

Failing Configuration

Exception Message
System.IO.IOException : Unexpected EOF trying to read request header
CallStack
   at System.Net.Test.Common.LoopbackServer.Connection.ReadRequestHeaderAsync()
   at System.Net.Test.Common.LoopbackServer.Connection.ReadRequestHeaderAndSendResponseAsync(HttpStatusCode statusCode, String additionalHeaders, String content)
   at System.Net.Test.Common.LoopbackServer.<>c__DisplayClass21_0.<<AcceptConnectionSendResponseAndCloseAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.Net.Test.Common.LoopbackServer.AcceptConnectionAsync(Func`2 funcAsync)
   at System.Net.Test.Common.LoopbackServer.AcceptConnectionAsync(Func`2 funcAsync)
   at System.Net.Test.Common.LoopbackServer.AcceptConnectionSendResponseAndCloseAsync(HttpStatusCode statusCode, String additionalHeaders, String content)
   at System.Net.Http.Functional.Tests.HttpClientHandlerTest_Http1.<SendAsync_HostHeader_First>b__1_0(LoopbackServer server, Uri url)
   at System.Net.Test.Common.LoopbackServer.CreateServerAsync(Func`2 funcAsync, Options options)
   at System.Net.Http.Functional.Tests.HttpClientHandlerTest_Http1.SendAsync_HostHeader_First()
--- End of stack trace from previous location ---
WasmTestOnChrome-ST-System.Net.Http.Functional.Tests.WorkItemExecution [Console] [Details] [Artifacts] [1.76% failure rate]
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]

Failing Configuration

Was this helpful? Yes No