Skip to content

Increase RemoteExecutor timeout for DiagnosticSource bridge tests#129704

Merged
tarekgh merged 2 commits into
dotnet:mainfrom
tarekgh:fix-diagnosticsource-remoteexecutor-timeout
Jun 23, 2026
Merged

Increase RemoteExecutor timeout for DiagnosticSource bridge tests#129704
tarekgh merged 2 commits into
dotnet:mainfrom
tarekgh:fix-diagnosticsource-remoteexecutor-timeout

Conversation

@tarekgh

@tarekgh tarekgh commented Jun 22, 2026

Copy link
Copy Markdown
Member

The default RemoteExecutor timeout of 60 seconds is not enough on some slower CI machines, which causes intermittent timeouts in the DiagnosticSource EventSource bridge tests (for example TestSamplingPrecedence).

This change introduces a shared RemoteInvokeOptions with a 3 minute timeout and applies it to all RemoteExecutor.Invoke calls in DiagnosticSourceEventSourceBridgeTests that previously relied on the default timeout.

Fixes #129687

The default RemoteExecutor timeout of 60 seconds is not enough on some slower CI machines, causing intermittent timeouts. Set a 3 minute timeout for all RemoteExecutor.Invoke calls in DiagnosticSourceEventSourceBridgeTests.

Fixes dotnet#129687

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates DiagnosticSourceEventSourceBridgeTests to use a shared RemoteInvokeOptions with an increased timeout (3 minutes) for RemoteExecutor-based subprocess tests, aiming to reduce intermittent timeouts on slower CI machines.

Changes:

  • Introduces a shared RemoteInvokeOptions instance with TimeOut = 180000ms.
  • Updates all RemoteExecutor.Invoke(...) calls in DiagnosticSourceEventSourceBridgeTests to pass the shared options instead of relying on the default timeout.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 22, 2026 18:26
@tarekgh
tarekgh requested a review from noahfalk June 22, 2026 18:28
@tarekgh tarekgh added this to the 11.0.0 milestone Jun 22, 2026
@dotnet-policy-service

Copy link
Copy Markdown
Contributor

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

@noahfalk

Copy link
Copy Markdown
Member

fyi @mdh1418 @lateralusX

@tarekgh
tarekgh merged commit 7f5d4c4 into dotnet:main Jun 23, 2026
92 of 97 checks passed
@dotnet-milestone-bot dotnet-milestone-bot Bot modified the milestones: 11.0.0, 11.0-preview6 Jun 23, 2026
eiriktsarpalis pushed a commit that referenced this pull request Jul 15, 2026
…29704)

The default RemoteExecutor timeout of 60 seconds is not enough on some
slower CI machines, which causes intermittent timeouts in the
DiagnosticSource EventSource bridge tests (for example
`TestSamplingPrecedence`).

This change introduces a shared `RemoteInvokeOptions` with a 3 minute
timeout and applies it to all `RemoteExecutor.Invoke` calls in
`DiagnosticSourceEventSourceBridgeTests` that previously relied on the
default timeout.

Fixes #129687

---------

Co-authored-by: Tarek Mahmoud Sayed <tarekms@ntdev.microsoft.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test failure: System.Diagnostics.Tests.DiagnosticSourceEventSourceBridgeTests.TestSamplingPrecedence

3 participants