Skip to content

Investigate shared restore races in parallel C# SDK regeneration - #11975

Draft
JoshLove-msft with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-azure-sdk-regeneration-races
Draft

JoshLove-msft with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-azure-sdk-regeneration-races

Conversation

Copilot AI commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Parallel SDK regeneration can restore shared projects such as Azure.SdkAnalyzers into the same intermediate directory, causing file conflicts and skipping subsequent batches.

  • Findings: Existing concurrency fixes isolate plugin builds and coordinate npm installation. The outer SDK restores still share intermediate paths, with no retry before skipping later batches.
  • Changes: None. This investigation checked whether the issue was already addressed; the inspected code indicates it remains unresolved.

@azure-pipelines

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

Copilot AI changed the title [WIP] Fix parallel Azure SDK regeneration races on shared MSBuild files Investigate shared restore races in parallel C# SDK regeneration Sep 15, 2026
Copilot AI requested a review from JoshLove-msft September 15, 2026 19:41
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.

[http-client-csharp] Parallel Azure SDK regeneration races on shared MSBuild intermediate files

2 participants