Skip to content

[release/9.0-staging] Give the nested process chain in ProcessWaitingTests depth-proportional wait budgets - #135632

Merged
ViveliDuCh merged 1 commit into
release/9.0-stagingfrom
backport/pr-135608-to-release/9.0-staging
Oct 12, 2026
Merged

ViveliDuCh merged 1 commit into
release/9.0-stagingfrom
backport/pr-135608-to-release/9.0-staging

Conversation

@github-actions

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

Copy link
Copy Markdown
Contributor

Fixes #118977

main PR #135608

Backport to release/9.0-staging.

/cc @ViveliDuCh @pcshrosbree

Description

The same WaitChain/WaitAsyncChain timeout failure seen in main also occurred in release/9.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.

@ViveliDuCh

Copy link
Copy Markdown
Member

/ba-g DeadLetter and unrelated failures tracked in #134011,  #131814 and #135649 

@ViveliDuCh ViveliDuCh added the Servicing-approved Approved for servicing release label Oct 12, 2026
@ViveliDuCh
ViveliDuCh merged commit 43d04e6 into release/9.0-staging Oct 12, 2026
87 of 95 checks passed
@ViveliDuCh
ViveliDuCh deleted the backport/pr-135608-to-release/9.0-staging branch October 12, 2026 22:31
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.

2 participants