Microsoft.WebTools.AspireService.Tests.SendLogMessageAsync_Test: intermittent hang (test host hang-dump timeout, exit code 7) #55477

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1527013
Leg Name: TestBuild: linux (x64) - ubuntu.2204.amd64.open — Helix work item Microsoft.WebTools.AspireService.Tests.dll
Helix job: 95dafd74-707a-47b0-873b-89d5d3110341
Pull request where encountered: #55458 (failed on a manual-retry run; the same suite passed on retry in build 1527662)

Summary

Microsoft.WebTools.AspireService.Tests SendLogMessageAsync_Test intermittently hangs. The rest of the assembly finishes quickly (12 completed, 0 failed) and SendLogMessageAsync_Test is the only test still running — it is logged as [slow] still running after 1m … 16m — when the blame hang-dump timeout of 00:48:00 fires. A hang dump is collected for the dotnet process, the test host is killed (exit code is '137'), and the Helix work item finishes with exit code 7, failing the Monitor Helix Jobs step and turning the whole build red.

The test appears to wedge waiting on the DCP session connection: the console shows [#1] Failed to send message: Connection not found (dcpId='myid') shortly before the test stops making progress. The failure is intermittent (passed on retry), so it is tracked with BuildRetry: true.

This is a sibling failure to #55258 (LoggingTests.BinaryLogs) and #55430 (MobileHotReloadTests.HotReload_WithWebSocketCapability) — same hang-dump / exit-code-7 mechanism, different test — so it is tracked separately with a test-specific pattern to avoid cross-matching.

Error Details

[#1] Failed to send message: Connection not found (dcpId='myid').
running... 12 completed, 0 failed | active: SendLogMessageAsync_Test
[slow] still running after 16m 00s: SendLogMessageAsync_Test (Microsoft.WebTools.AspireService.Tests.dll|net11.0|x64)
Hang dump timeout of '00:48:00' expired
Dumping process 6813 - dotnet
The following tests were still running when dump was taken (format: [<time-elapsed-since-start>] <name>):
[00:48:00] SendLogMessageAsync_Test
Creating dump file '/datadisks/disk1/work/AD0E08E8/w/C1800A66/e/dotnet_6813_hang.dmp'
...
Test host crashed; recovered 12 test result(s) from the TRX streaming sidecar (additional results that were in flight at crash time may be missing).
Test application process didn't exit gracefully, exit code is '137'
+ export _commandExitCode=7
+ exit 7
['Microsoft.WebTools.AspireService.Tests.dll' END OF WORK ITEM LOG: Command exited with 7]

AzDO reported:

Work item 'Microsoft.WebTools.AspireService.Tests.dll' in job 'Linux x64 - ubuntu.2204.amd64.open' failed (Finished, exit code 7).

Error Message

{
    "ErrorMessage": [
        "Hang dump timeout of",
        "] SendLogMessageAsync_Test",
        "END OF WORK ITEM LOG: Command exited with 7"
    ],
    "BuildRetry": true,
    "ExcludeConsoleLog": false
}

The multi-line pattern requires, in order: the blame hang-dump timeout message, SendLogMessageAsync_Test reported as still-running when the dump was taken, and the work item exiting with code 7 — which together uniquely identify a hang caused by this specific test without matching unrelated failures (e.g. the BinaryLogs hang tracked by #55258 or the HotReload_WithWebSocketCapability hang tracked by #55430). Validated with Test-KnownIssuePattern.ps1 against the failing work item console log (RESULT: PASS).

ExcludeConsoleLog is false because these lines appear only in the Helix work-item console log, not the AzDO build log.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1527013
Error message validated: [Hang dump timeout of ] SendLogMessageAsync_Test END OF WORK ITEM LOG: Command exited with 7]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 7/27/2026 12:59:41 PM UTC

Report

Summary