-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Settings_MaxConcurrentStreamsGet_Server test failure #27379
Comments
Thanks for contacting us. |
One thing that might help make these HttpClientHttp2InteropTests more reliable (but probably won't fix this issue) is to use SocketHttpHandler's new ConnectCallback to wire it up with Kestrel's in-memory test transport like Http2EndToEndTests does. aspnetcore/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2EndToEndTests.cs Lines 47 to 61 in 540680a
If we do that, we should move it into InMemory.FunctionalTests. |
We'll see what happens with dotnet/runtime#44669 before deciding what to do with this test. |
Runtime fixed the issue, we should be able to unquarantine. |
Passing for past 30 days and Runtime issue that was causing it has been fixed. #27379
The text was updated successfully, but these errors were encountered: