Skip to content

Limit dotnet-new integration test parallelism - #56009

Draft
nagilson with Copilot wants to merge 2 commits into
mainfrom
copilot/dotnet-new-integration-test-timeout-fix
Draft

Limit dotnet-new integration test parallelism#56009
nagilson with Copilot wants to merge 2 commits into
mainfrom
copilot/dotnet-new-integration-test-timeout-fix

Conversation

Copilot AI commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

The dotnet-new Linux Helix work item timed out while running template integration tests. Class-level parallelism allowed too many resource-intensive dotnet and MSBuild child processes to compete concurrently.

  • Bound resource usage
    • Limit MSTest execution to two workers.
    • Preserve class-level parallelism while reducing Helix resource contention.
<MSTestParallelizeScope>ClassLevel</MSTestParallelizeScope>
<MSTestParallelizeWorkers>2</MSTestParallelizeWorkers>

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
3 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Co-authored-by: nagilson <23152278+nagilson@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix timeout issue in DotnetCSharpClassTemplatesTest Limit dotnet-new integration test parallelism Aug 28, 2026
Copilot AI requested a review from nagilson August 28, 2026 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

2 participants