Reduce CI test parallelism cap from 8 to 4#714
Merged
Conversation
Lower contention on CI agents to reduce timing-coupled and connection race flakiness. The test suite spawns out-of-process compatibility binaries and many short-lived loopback TCP connections; at 6+ in-flight tests on an 8 vCPU agent this regularly produces ephemeral-port and TcpClientManager dispose races that show up as "connection forcibly closed" failures, plus Stopwatch-vs-wall-clock drift on Windows 2012R2 guests under load. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Test run completed first run in ~28m. |
LukeButters
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
LevelOfParallelismInTeamCity()cap from 8 to 4 inCustomLevelOfParallelismAttribute. On our 8 vCPUStandard_D8as_v4agent this drops in-flight tests from 6 to 4.TcpClientManagerdispose races and Stopwatch-vs-wall-clock drift seen on Windows 2012R2 under load. Filed in isolation (offmain, not stacked on EFT-3214's other branch) so the effect on the next CI run is observable on its own.Test plan
HalibutTimeoutsAndLimits_AppliesToTcpClientReceiveTimeout,WhenThenNetworkIsPaused_*) for whetherStopwatch.Elapsedassertions now hold🤖 Generated with Claude Code