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

[CI] Test failure from System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #101567

Closed
kouvel opened this issue Apr 25, 2024 · 17 comments
Assignees
Labels
area-System.Net.Quic blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@kouvel
Copy link
Member

kouvel commented Apr 25, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=655031
Build error leg or test failing: Build / Libraries Test Run release coreclr windows x64 Debug / Send to Helix
Pull request: #101501

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "System.Net.Quic.QuicException : The connection timed out from inactivity.",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=655031
Error message validated: [System.Net.Quic.QuicException : The connection timed out from inactivity.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/25/2024 8:21:21 PM UTC

Report

Build Definition Test Pull Request
655218 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101318
655926 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #101540
656345 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #101568
656316 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_Finalization_Http3.IncompleteResponseStream_ResponseDropped_CancelsRequestToServer #101513
656320 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101294
656230 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101188
655011 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101221
656221 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101450
656213 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101381
656209 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #100266
656202 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101557
656219 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #100389
656161 dotnet/runtime System.Net.Http.Functional.Tests.WorkItemExecution #101531
656061 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream
656049 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #100141
655951 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101545
655948 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101545
655753 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #101133
655731 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101053
655722 dotnet/runtime System.Net.Quic.Functional.Tests.WorkItemExecution
655689 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101478
655692 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent #101531
655700 dotnet/runtime System.Net.Quic.Functional.Tests.WorkItemExecution
655709 dotnet/runtime System.Net.Quic.Functional.Tests.WorkItemExecution
655669 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101392
655619 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101531
655583 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Cookies_Http3.GetAsync_DefaultCoookieContainer_NoCookieSent
655445 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream #101525
655365 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101450
655360 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101451
655225 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101450
655080 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101512
653929 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream #101418
655003 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream #101507
655031 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandler_AltSvc_Test_Http3.AltSvc_Header_Upgrade_Success #101501
653237 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.ReadAsStreamAsync_HandlerProducesWellBehavedResponseStream #101390
652467 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Headers_Http3.SendAsync_Expires_Success #101308

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
25 37 37
@kouvel kouvel added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-System.Net.Quic Known Build Error Use this to report build issues in the .NET Helix tab labels Apr 25, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 25, 2024
Copy link
Contributor

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

@CarnaViire
Copy link
Member

Should be a dupe of #91757

@kouvel
Copy link
Member Author

kouvel commented Apr 25, 2024

Ah ok. I think the main difference is #91757 is using ErrorPattern but the pattern doesn't look like a regex, so it wouldn't have matched the ErrorMessage string in this issue.

@kouvel
Copy link
Member Author

kouvel commented Apr 25, 2024

Actually nevermind, it seems like that should have matched the error message, not sure why it wouldn't have.

@CarnaViire
Copy link
Member

image
I believe it was matched

@CarnaViire
Copy link
Member

Oh, it's a different test it seems 🙈

@kouvel
Copy link
Member Author

kouvel commented Apr 25, 2024

Oh is the test taken into account somehow? I thought it was just based on the message/pattern.

@CarnaViire
Copy link
Member

Oh is the test taken into account somehow? I thought it was just based on the message/pattern.

Hmmm you're right. The column with the test name confused me.

Then it should have been matched -- as the build in question is present in the table... 🤔

@kouvel
Copy link
Member Author

kouvel commented Apr 25, 2024

The build analysis in my PR #101501 did not recognize this as a known issue (at least in attempt 3, though I saw the same failure in the first two). I had rerun it again.

@kouvel
Copy link
Member Author

kouvel commented Apr 25, 2024

I mean in attempt 3 that was the only failure that the build analysis pointed out as unknown, so that's a bit puzzling.

@JulieLeeMSFT
Copy link
Member

@CarnaViire, can we close this issue because you merged #101569?

@CarnaViire
Copy link
Member

@JulieLeeMSFT I'd close this one as it should be all matched to #91757 -- in case it wouldn't happen, can you please tag someone from the "Known Issues" team so they can help troubleshoot?

As for #101569 -- we need first to verify that the timeouts went away or at least subsided (after the change propagates). And even then, there's going to be quite an untrivial investigation. So at least #91757 would be open as a tracking issue for the investigation.

@CarnaViire
Copy link
Member

Duplicate of #91757

@CarnaViire CarnaViire marked this as a duplicate of #91757 Apr 26, 2024
@CarnaViire CarnaViire closed this as not planned Won't fix, can't repro, duplicate, stale Apr 26, 2024
@dotnet-policy-service dotnet-policy-service bot removed the untriaged New issue has not been triaged by the area owner label Apr 26, 2024
@AlitzelMendez
Copy link
Member

@JulieLeeMSFT I'd close this one as it should be all matched to #91757 -- in case it wouldn't happen, can you please tag someone from the "Known Issues" team so they can help troubleshoot?

As for #101569 -- we need first to verify that the timeouts went away or at least subsided (after the change propagates). And even then, there's going to be quite an untrivial investigation. So at least #91757 would be open as a tracking issue for the investigation.

could you please provide more details on the expectation of this known issue? like sharing a build that you were expecting this issue would match

I compared with the other known issue that you shared but they have a different error message, this one has an ErrorMessage and the other issue has an ErrorPattern which is slightly different so it is naturally that the match different builds, but if you were expecting a particular build please share it with me so I can take a look

@kouvel
Copy link
Member Author

kouvel commented Apr 26, 2024

Here's some info about the failure that wasn't matched to #91757:

Even though #91757 is using ErrorPattern, treating it as a regex the expectation was that it would still match the error message in the console log: System.Net.Quic.QuicException : The connection timed out from inactivity.

@kouvel
Copy link
Member Author

kouvel commented Apr 26, 2024

I'm not sure how to access the build analysis from previous build attempts. If there's a way, the 3rd attempt would show the failure as some that is not a known failure.

@CarnaViire
Copy link
Member

the other issue has an ErrorPattern which is slightly different

As @kouvel also mentioned above, the regex in #91757 is
"ErrorPattern": "System.Net.Quic.QuicException ?: The connection timed out from inactivity"
And applying the validation suggested in https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssueJsonStepByStep.md#how-to-create-a-known-issue-step-by-step you can see that it matches
image
unless we're missing something @AlitzelMendez

@karelz karelz added this to the 9.0.0 milestone May 14, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Quic blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

5 participants