Skip to content

Conversation

@drewnoakes
Copy link
Member

On a busy machine, one second might not be enough for this unit test to complete successfully. I observed this test fail in a pipeline run, so it seems a good idea to increase it slightly, as the cost of a false negative is high.

On a busy machine, one second might not be enough for this unit test to
complete successfully. I observed this test fail in a pipeline run, so
it seems a good idea to increase it slightly, as the cost of a false
negative is high.
@drewnoakes drewnoakes added this to the 18.3 milestone Nov 17, 2025
@drewnoakes drewnoakes requested a review from a team as a code owner November 17, 2025 05:18
@drewnoakes drewnoakes added Feature-Language-Service Populating the Roslyn workspace with references, source files, analyzers, etc Area-Testing Relates to testing and does not affect product code. labels Nov 17, 2025
@drewnoakes drewnoakes enabled auto-merge November 17, 2025 05:21
@drewnoakes drewnoakes merged commit 1831049 into dotnet:main Nov 17, 2025
5 checks passed
@drewnoakes drewnoakes deleted the increase-unit-test-timeout branch November 17, 2025 17:15
@dotnet-policy-service dotnet-policy-service bot modified the milestones: 18.3, 18.1 Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Testing Relates to testing and does not affect product code. Feature-Language-Service Populating the Roslyn workspace with references, source files, analyzers, etc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants