-
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
Regression test: ConnectTimeout_PlaintextStreamFilterTimesOut_Throws #55931
Labels
area-System.Net.Http
disabled-test
The test is disabled in source code against the issue
test-run-core
Test failures in .NET Core test runs
Milestone
Comments
dotnet-issue-labeler
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jul 19, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsTypes:
Failures 5/19-7/18 (incl. PRs):
@geoffkizer this looks like regression from your Connection PR -- can you please take a look?
|
karelz
added a commit
that referenced
this issue
Jul 19, 2021
Disable test ConnectTimeout_PlaintextStreamFilterTimesOut_Throws Disabled test tracked by #55931
stephentoub
pushed a commit
that referenced
this issue
Jul 20, 2021
Disable test ConnectTimeout_PlaintextStreamFilterTimesOut_Throws Disabled test tracked by #55931
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 20, 2021
karelz
added
test-run-core
Test failures in .NET Core test runs
disabled-test
The test is disabled in source code against the issue
labels
Jul 20, 2021
Test disabled in PR #55932 on 7/20 |
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 21, 2021
ghost
locked as resolved and limited conversation to collaborators
Aug 20, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-System.Net.Http
disabled-test
The test is disabled in source code against the issue
test-run-core
Test failures in .NET Core test runs
Types:
Failures 5/19-7/18 (incl. PRs):
@geoffkizer this looks like regression from your Connection PR -- can you please take a look?
The text was updated successfully, but these errors were encountered: