[AI discovered CI] dotnet-new integration test work item times out during DotnetCSharpClassTemplatesTest

## Build Information

- Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1573087
- Branch: `refs/heads/main`
- Failing work item: `dotnet-new.IntegrationTests.dll.1` on Linux x64 (`ubuntu.2204.amd64.open`)
- Test: `DotnetCSharpClassTemplatesTest ("interface")`
- Phase: `test-execution`
- Failure type: `timeout`
- Evidence sources: `helix-console`, `process-exit-code`, `helix-trx`, `helix-dump`
- **Failure fingerprint:** `test-execution|timeout|dotnet-new.integrationtests.dll.|process-id-155316hang-dump-timeout-of----expired-the-following-tests-were-still-running-when-dump-was-taken-format--test-host-crashed-reco`
- Matching prior build links reviewed for history: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1572955, https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1572757

## Failure History

- Current matching occurrence: 1 (build 1573087).
- Surrounding sequence: builds 1572955 and 1572757 passed; current build 1573087 failed.
- Related dotnet-new failures in builds 1571404, 1570554 used distinct network/service mechanisms and are not counted as recurrence of this timeout.
- The sequence establishes an actionable timeout, but does not establish recurrence or an underlying cause.

## Error Details

Exact excerpt: `Process ID: 155316Hang dump timeout of '00:48:00' expired`; `Test host crashed; recovered 49 test result(s) from the TRX streaming sidecar`; `Test application process didn't exit gracefully, exit code is '137'`; active test: `[00:48:01] DotnetCSharpClassTemplatesTest ("interface")`.

- Exit code: 137
- Console: https://helix.dot.net/api/jobs/9a785f6d-4219-4d1b-8463-882d6ee8733e/workitems/dotnet-new.IntegrationTests.dll.1/files/console.0d316844.log?api-version=2019-06-17
- Dump: https://helix.dot.net/api/jobs/9a785f6d-4219-4d1b-8463-882d6ee8733e/workitems/dotnet-new.IntegrationTests.dll.1/files/dotnet_153293_hang.dmp?api-version=2019-06-06
- TRX: https://helix.dot.net/api/jobs/9a785f6d-4219-4d1b-8463-882d6ee8733e/workitems/dotnet-new.IntegrationTests.dll.1/files/dotnet-new.IntegrationTests_net11.0_x64.trx?api-version=2019-06-17

## Root Cause Analysis

**Observed:** The Linux dotnet-new integration-test work item exceeded the 48-minute hang-dump timeout while `DotnetCSharpClassTemplatesTest ("interface")` was still running. The host exited with code 137 after a dump was collected; 49 results were recovered and all recovered tests passed.

**Assessment:** The proximate cause is a non-graceful test-host termination after the Helix hang timeout. The dossier does not establish whether the test itself hung, the process was resource constrained, or an external condition prevented completion. The generic `Monitor Helix Jobs` failure is a downstream report, not the cause.

**Confidence:** Medium for the timeout and host termination; Low for the underlying trigger.

**Alternatives / Unknowns:** The dump has not been analyzed. It is unknown whether the test was blocked in template generation, child-process/IPC activity, filesystem or network I/O, or resource exhaustion. No target-branch comparison or changed-file correlation is provided.

## Suggested Investigation

1. Analyze `dotnet_153293_hang.dmp` and the final console/TRX timing to identify the blocked thread and child process state.
2. Re-run the specific test/work item on the same Linux queue and compare with a target-branch or adjacent successful run.
3. Inspect the test implementation and recent changes affecting C# class templates, process invocation, or test parallelism; check resource and filesystem telemetry before changing the timeout.

> Generated by [🕵️ CI Quality Investigator](https://github.com/dotnet/sdk/actions/runs/33213284720) · gpt56 · 1.58 AIC · ⌖ 0.967 AIC · ⊞ 30.5K · [◷](https://github.com/search?q=repo%3Adotnet%2Fsdk+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Fsdk%2Fci-quality-monitor%22&type=issues)