-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_PingKeepAlive(keepAlivePingDelay: 00:00:01, keepAlivePingPolicy: WithActiveRequests, expectRequestFail: False) #41929
Comments
Tagging subscribers to this area: @dotnet/ncl |
This comment has been minimized.
This comment has been minimized.
Triage: probably test issue, it's timing dependent since it's testing background process. |
This comment has been minimized.
This comment has been minimized.
There's been spike of errors in the last 2 days:
34 errors in the last two days. |
This comment has been minimized.
This comment has been minimized.
Disabled in #45214 |
This comment has been minimized.
This comment has been minimized.
it seems like the last failure is on release/5.0 Is there guidance @danmosemsft how much effort we want to put into that branch? One strategy could be to disable all flaky tests and focus on stabilization in master. If we car, I would also expect we should log 5.0 bugs separate? |
We will be servicing 5.0 until about Feb 2022 so we will still need to run PR validation a few 100 times over that time. In general I think this means if a test is significantly flaky we generally either disable it (as long as we still get reasonably coverage) or backport a test fix if any. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Summary of details and history:
|
Completely redesign tests for HTTP/2 KeepAlive PING, so they: - Work well with RTT pings introduced in Implement dynamic HTTP/2 window scaling #54755 - Run sequentially, reducing the chance of failing because of timing issues caused by parallel workloads - Are better organized: multiple test cases for different scenarios, instead of one theory with complex branches on parameters Instead of reading / reacting to frames inline, there is a separate Task for processing incoming frames, responding to PING immediately and pushing other frames to a Channel<Frame>. Fixes #41929
failed in job: runtime-libraries-coreclr outerloop 20200906.1
net5.0-Linux-Release-arm64-CoreCLR_release-(Alpine.312.Arm64.Open)ubuntu.1804.armarch.open@mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-arm64v8-20200602002604-25f8a3e
Error message
The text was updated successfully, but these errors were encountered: