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] Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException #92647

Closed
rzikm opened this issue Sep 26, 2023 · 1 comment · Fixed by #94112
Closed
Assignees
Labels
area-System.Net.Http 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

@rzikm
Copy link
Member

rzikm commented Sep 26, 2023

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=417421
Build error leg or test failing: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException

Error Message

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

{
  "ErrorMessage": "System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException [FAIL]",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=417421
Error message validated: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException [FAIL]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/26/2023 3:12:06 PM UTC

Report

Build Definition Test Pull Request
447249 dotnet/runtime System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException #86391

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 1
@rzikm rzikm added 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 labels Sep 26, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Sep 26, 2023
@ghost
Copy link

ghost commented Sep 26, 2023

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

Issue Details

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=417421
Build error leg or test failing: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException

Error Message

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

{
  "ErrorMessage": "System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_IncorrectServerPreface_RequestFailsWithAppropriateHttpProtocolException [FAIL]",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Author: rzikm
Assignees: -
Labels:

area-System.Net.Http, blocking-clean-ci, untriaged, Known Build Error

Milestone: -

@ManickaP ManickaP removed the untriaged New issue has not been triaged by the area owner label Oct 2, 2023
@ManickaP ManickaP added this to the 9.0.0 milestone Oct 2, 2023
@wfurt wfurt self-assigned this Oct 25, 2023
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Oct 27, 2023
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Oct 31, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Dec 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Http 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

Successfully merging a pull request may close this issue.

3 participants