[test-quarantine] Quarantine flaky IISExpress RequestResponseTests class - #68272
Open
github-actions[bot] wants to merge 1 commit into
Open
[test-quarantine] Quarantine flaky IISExpress RequestResponseTests class#68272github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
requested review from
BrennanConroy and
halter73
as code owners
August 7, 2026 10:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Quarantines the
Microsoft.AspNetCore.Server.IIS.IISExpress.FunctionalTests.RequestResponseTestsclass (class-level[QuarantinedTest]) due to widespread, shared connection-refused/reset failures observed across 36 of its test methods in recent CI runs (71 combined failures).All failures share the same 1-2 build IDs and the same underlying connection errors (
SocketException: connection actively refused,IOException: connection forcibly closed), pointing at a shared IIS Express test fixture/connection issue rather than 36 independent test bugs. None of the affected tests are flagged as consistent regressions.Tracking issue: #68271
See tracking issue for the full failure analysis and list of affected methods.