You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test sends a POST request one character at a time (10ms between each character) to simulate a slow connection. It has been failing intermittently by receiving an empty string instead of HTTP/1.1 200 OK response headers. This is consistent with IISExpress timing issues under CI load, where the slow-connection simulation interacts with connection timeouts or thread scheduling.
The using Microsoft.AspNetCore.InternalTesting; statement was already present in the file.
The patch file is available in the agent artifact in the workflow run linked above.
To create a pull request with the changes:
# Download the artifact from the workflow run
gh run download 24028854426 -n agent -D /tmp/agent-24028854426
# Create a new branch
git checkout -b quarantine/2026-04-06-iis-read-write-slow-11791a9a9c47cbcc
# Apply the patch (--3way handles cross-repo patches where files may already exist)
git am --3way /tmp/agent-24028854426/aw-quarantine-2026-04-06-iis-read-write-slow.patch
# Push the branch to origin
git push origin quarantine/2026-04-06-iis-read-write-slow-11791a9a9c47cbcc
# Create the pull request
gh pr create --title '[test-quarantine] Quarantine IISExpress RequestResponseTests.ReadAndWriteSlowConnection' --base main --head quarantine/2026-04-06-iis-read-write-slow-11791a9a9c47cbcc --repo DeagleGross/aspnetcore
Show patch (36 lines)
From 2fe7bb9fc262eb428fadb27e6de7103abcbb2223 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 6 Apr 2026 11:21:41 +0000
Subject: [PATCH] Quarantine RequestResponseTests.ReadAndWriteSlowConnection
The test sends a request character-by-character (slow connection simulation)
and has been failing intermittently in IISExpress.FunctionalTests, receiving
an empty string instead of HTTP response headers (2 failures in 30 days).
This is consistent with a timing/connection issue in IISExpress under CI
load, where the slow-connection simulation interacts poorly with connection
timeouts or thread scheduling.
Associated issue: https://github.com/DeagleGross/aspnetcore/issues/162
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
.../IIS/IIS/test/Common.FunctionalTests/RequestResponseTests.cs | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/Servers/IIS/IIS/test/Common.FunctionalTests/RequestResponseTests.cs b/src/Servers/IIS/IIS/test/Common.FunctionalTests/RequestResponseTests.cs
index 4179953dcf..f7b2d3cda5 100644
--- a/src/Servers/IIS/IIS/test/Common.FunctionalTests/RequestResponseTests.cs+++ b/src/Servers/IIS/IIS/test/Common.FunctionalTests/RequestResponseTests.cs@@ -214,6 +214,7 @@ public class RequestResponseTests
}
[ConditionalFact]
+ [QuarantinedTest("https://github.com/DeagleGross/aspnetcore/issues/162")]
public async Task ReadAndWriteSlowConnection()
{
using (var connection = _fixture.CreateTestConnection())
--
2.53.0
Quarantines a flaky IIS connection test:
IISExpress.FunctionalTests.RequestResponseTests.ReadAndWriteSlowConnectionThe test sends a POST request one character at a time (10ms between each character) to simulate a slow connection. It has been failing intermittently by receiving an empty string instead of
HTTP/1.1 200 OKresponse headers. This is consistent with IISExpress timing issues under CI load, where the slow-connection simulation interacts with connection timeouts or thread scheduling.The
using Microsoft.AspNetCore.InternalTesting;statement was already present in the file.Associated issue: #162
Note
🔒 Integrity filter blocked 19 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Note
This was originally intended as a pull request, but the git push operation failed.
Workflow Run: View run details and download patch artifact
The patch file is available in the
agentartifact in the workflow run linked above.To create a pull request with the changes:
Show patch (36 lines)