Skip to content

[ci-scan] Test failure: System.Net.Tests.HttpResponseStreamTests.Write_ContentToClosedConnectionSynchronously_ThrowsHttpListener [Content truncated due to length] #130278

Closed

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1494308
Build error leg or test failing: maccatalyst-x64 Release AllSubsets_NativeAOT - System.Net.HttpListener.Tests

Error Details

On the Apple NativeAOT library-test legs (maccatalyst / iossimulator AllSubsets_NativeAOT), HttpResponseStreamTests.Write_ContentToClosedConnectionSynchronously_ThrowsHttpListenerException fails its Assert.Throws check. Writing to an already-closed connection does not raise on the Darwin/Apple socket stack, so the expected HttpListenerException is never thrown:

[FAIL] System.Net.Tests.HttpResponseStreamTests.Write_ContentToClosedConnectionSynchronously_ThrowsHttpListenerException(ignoreWriteExceptions: False)
Assert.Throws() Failure: No exception was thrown
Expected: typeof(System.Net.HttpListenerException)
   at System.Net.Tests.HttpResponseStreamTests.<Write_ContentToClosedConnectionSynchronously_ThrowsHttpListenerException>d__20.MoveNext() in /_/src/libraries/System.Net.HttpListener/tests/HttpResponseStreamTests.cs:line 449

The test carries [ActiveIssue(".../issues/21590", TestPlatforms.OSX | TestPlatforms.FreeBSD)], but that skip does not include TestPlatforms.MacCatalyst, so it runs and fails on the maccatalyst NativeAOT leg. NativeAOT library tests on Apple mobile were newly enabled by #125437 (merged 2026-07-02); the failure first appears on build 1492684 (2026-07-03) and reproduces on follow-up build 1494829. The ...Asynchronously... sibling variant of the same behavioural difference is catalogued in the Apple-mobile NativeAOT tracker #126697. Sibling Apple-NativeAOT library-test failures from the same source build are tracked by #130253 and #130254.

First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1492684

Related: #126697

Error Message

{
  "ErrorMessage": [
    "[FAIL] System.Net.Tests.HttpResponseStreamTests.Write_ContentToClosedConnectionSynchronously_ThrowsHttpListenerException",
    "Expected: typeof(System.Net.HttpListenerException)"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Note

🔒 Integrity filter blocked 31 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #107364 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #107364 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #114222 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #127541 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #112093 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #119449 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #130105 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #93686 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #76917 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #71338 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #83890 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #71472 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #78657 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #80356 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #10055 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #56073 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • ... and 15 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 18.6M · ◷

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Activity

  1. JulieLeeMSFT commented on Jul 7, 2026

    @JulieLeeMSFT
    Member

    @kotlarmilos, please activate area bot for these new issues.

  2. added and removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 7, 2026
  3. dotnet-policy-service commented on Jul 7, 2026

    @dotnet-policy-service
    Contributor

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

  4. github-actions commented on Jul 8, 2026

    @github-actions
    ContributorAuthor

    Workflow artifact: ci-fix
    Artifact kind: handoff
    Linked KBE: #130278

    Note

    AI/Copilot-generated root-cause hand-off (ci-failure-fix). No automated code change was produced: the only in-bounds options would be to extend an [ActiveIssue] skip to MacCatalyst (muting) or to change Darwin socket behavior (out of bounds), so I am looping in owners instead.

    Root cause (read-only analysis)

    On the Apple NativeAOT library-test legs (maccatalyst / iossimulator AllSubsets_NativeAOT, build 1494308), System.Net.Tests.HttpResponseStreamTests.Write_ContentToClosedConnectionSynchronously_ThrowsHttpListenerException fails:

    Assert.Throws() Failure: No exception was thrown
    Expected: typeof(System.Net.HttpListenerException)
       at .../HttpResponseStreamTests.cs:line 449
    

    The test writes to an already-closed connection and expects an HttpListenerException. On the Darwin/Apple socket stack the synchronous write to a closed connection does not raise, so no exception is thrown and the assert fails.

    The test already carries [ActiveIssue(".../issues/21590", TestPlatforms.OSX | TestPlatforms.FreeBSD)], but that platform mask does not include TestPlatforms.MacCatalyst, so it runs on the maccatalyst leg. This is the same behavioral difference already catalogued (async sibling) in #126697.

    Both conceivable changes are out of scope for this workflow:

    • Extending the [ActiveIssue] mask to MacCatalyst would mute the test — not allowed here.
    • Making the Darwin socket path raise on write-to-closed is a product/behavioral change well outside small-fix bounds.

    Whether MacCatalyst should simply inherit the existing OSX skip (all Darwin) is a maintainer judgement, so I am handing off rather than editing the skip.

    Evidence

    Suggested reviewers / area contacts

    Note

    🔒 Integrity filter blocked 17 items

    The following items were blocked because they don't meet the GitHub integrity level.

    • #128501 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #104998 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #104750 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #97491 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #76276 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #78999 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #76417 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #69571 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #62435 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #61444 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #35376 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #193 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #34218 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #38914 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #44747 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • [ci-scan] Test failure: System.Threading.Tests.MutexTests.CrossProcess_NamedMutex_ConcurrentCreateOrOpen #130125 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • ... and 1 more item

    To allow these resources, lower min-integrity in your GitHub frontmatter:

    tools:
      github:
        min-integrity: approved  # merged | approved | unapproved | none

    Generated by CI Outer-Loop Failure Fixer · ● 9.3M · ◷

  5. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Aug 10, 2026
  6. jeffschwMSFT commented on Aug 10, 2026

    @jeffschwMSFT
    Member

    removing blocking-clean-ci as it has not failed in 30 days

    Summary
    24-Hour Hit Count 7-Day Hit Count 1-Month Count
    0 0 0

  7. locked and limited conversation to collaborators on Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions