Skip to content

[release/11.0] Give the nested process chain in ProcessWaitingTests depth-proportional wait budgets - #135643

Merged
ViveliDuCh merged 1 commit into
release/11.0from
backport/pr-135608-to-release/11.0
Oct 13, 2026
Merged

ViveliDuCh merged 1 commit into
release/11.0from
backport/pr-135608-to-release/11.0

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Backport of #135608 to release/11.0

/cc @ViveliDuCh @pcshrosbree

The same WaitChain/WaitAsyncChain timeout failure seen in main also occurred in release/11.0. Scale each wait budget by the number of nested processes it covers.

Customer Impact

  • Customer reported
  • Found internally

Intermittent CI test failures; no product behavior change.

Regression

  • Yes
  • No

Existing test timeout issue; no known product regression.

Testing

#135608 reports both chain tests passing on Windows x86, Linux x64, and macOS arm64. No additional local tests run for this backport; CI is still in progress and currently has failures.

Risk

Low: test-only timeout adjustment. Assertions and product code are unchanged.

…al wait budgets (#135608)

Fixes #118977

## Problem

`ProcessWaitingTests.WaitChain` and `WaitAsyncChain` start a four-deep
chain of `RemoteExecutor` processes, and every level waits with the same
`WaitInMS`. The root's wait has to cover the start-up, work and exit of
all four processes while the leaf's covers one, so the root has the
leaf's budget while covering four lifetimes. 

## Change

Give each waiter `WaitInMS` per process beneath it: leaf 1×, then 2×, 3×
and 4× at the root.

> [!NOTE]
> This PR was prepared with AI assistance (Anthropic Claude, checked by
OpenAI Codex) at my request. I reviewed the change and the measurements
before opening it.
@azure-pipelines

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

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.

@adamsitnik adamsitnik left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you for backporting it @ViveliDuCh !

@adamsitnik adamsitnik added this to the 11.0.0 milestone Oct 13, 2026
@ViveliDuCh

Copy link
Copy Markdown
Member

/ba-g Only known failures

@ViveliDuCh ViveliDuCh added the Servicing-approved Approved for servicing release label Oct 13, 2026
@ViveliDuCh
ViveliDuCh merged commit 0d1d8e2 into release/11.0 Oct 13, 2026
88 of 93 checks passed
@ViveliDuCh
ViveliDuCh deleted the backport/pr-135608-to-release/11.0 branch October 13, 2026 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants