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.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.AfterReadResponseServerError_ClientWrite #85233

Closed
v-wenyuxu opened this issue Apr 24, 2023 · 3 comments
Labels
arch-arm64 area-System.Net.Http JitStress CLR JIT issues involving JIT internal stress modes os-windows test-bug Problem in test source code (most likely)
Milestone

Comments

@v-wenyuxu
Copy link

Failed in: runtime-coreclr libraries-jitstress 20230423.1

Failed tests:

net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2_tiered-Windows.11.Arm64.Open
    - System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.AfterReadResponseServerError_ClientWrite

Error message:

 Assert.Throws() Failure
Expected: typeof(System.IO.IOException)
Actual:   (No exception was thrown)

Stack trace:

    at System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.AfterReadResponseServerError_ClientWrite() in /_/src/libraries/System.Net.Http.WinHttpHandler/tests/FunctionalTests/BidirectionStreamingTest.cs:line 146
--- End of stack trace from previous location ---

@v-wenyuxu v-wenyuxu added arch-arm64 os-windows JitStress CLR JIT issues involving JIT internal stress modes labels Apr 24, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Apr 24, 2023
@ghost
Copy link

ghost commented Apr 24, 2023

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

Issue Details

Failed in: runtime-coreclr libraries-jitstress 20230423.1

Failed tests:

net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2_tiered-Windows.11.Arm64.Open
    - System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.AfterReadResponseServerError_ClientWrite

Error message:

 Assert.Throws() Failure
Expected: typeof(System.IO.IOException)
Actual:   (No exception was thrown)

Stack trace:

    at System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.AfterReadResponseServerError_ClientWrite() in /_/src/libraries/System.Net.Http.WinHttpHandler/tests/FunctionalTests/BidirectionStreamingTest.cs:line 146
--- End of stack trace from previous location ---

Author: v-wenyuxu
Assignees: -
Labels:

arch-arm64, area-System.Net.Http, os-windows, JitStress

Milestone: -

@ManickaP
Copy link
Member

Based on Kusto data, we've getting this error sporadically for a while (oldest occurrence is from 12/22). It happens only on Windows Arm 64. It might be timing issue between receiving the RST frame and sending some data here, i.e. test bug:

// Server sends RST_STREAM.
await connection.WriteFrameAsync(new RstStreamFrame(FrameFlags.EndStream, 0, streamId));
await Assert.ThrowsAsync<IOException>(() => requestStream.WriteAsync(new byte[50]).AsTask());

Triage: moving to future, we can bump the priority if starts occurring more often.

@ManickaP ManickaP added test-bug Problem in test source code (most likely) and removed untriaged New issue has not been triaged by the area owner labels Apr 24, 2023
@ManickaP ManickaP added this to the Future milestone Apr 24, 2023
@MihaZupan
Copy link
Member

Closing as duplicate of #86262 as that one already gets build-analysis updates on impacted PRs.

@karelz karelz modified the milestones: Future, 8.0.0 May 27, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jun 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-arm64 area-System.Net.Http JitStress CLR JIT issues involving JIT internal stress modes os-windows test-bug Problem in test source code (most likely)
Projects
None yet
Development

No branches or pull requests

4 participants