Repository navigation
Conversation
Split each job's classes across processes, each with its own database, so tests that must run serially within a process run side by side. Balance shards and processes using committed timings, give EndToEndTests more shards as its hosts need fixed ports, and pull the Postgres image during the build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Changes to pr.yml or RunTests.cs don't touch any project, so they would otherwise skip all tests while changing how every test runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
At 45 seconds Api.IntegrationTests fell just inside a single shard and became the longest job, limited by CPU rather than serial tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Tests in
DisableParallelizationcollections run one at a time and make up most of CI's test time: 150s of the 156sCore.Teststakes. Each process now has its own database (#3999), so they can run side by side in separate processes.scripts/RunTests.cs, which splits a job's classes across up to 4 processes; this replaces the shard logic inpr.ymland thetestcomposite actiontests/test-timings.jsonto balance classes and set shard counts, refreshed withjust update-test-timings <run ID>; it's committed because tests don't run onmain, and a class with no timing is estimated from its test countEndToEndTestsat one process per job since its hosts use fixed ports; timings give it 5 shards rather than 3just test-project Core.Testsfor the same split locallypr.ymlorRunTests.cschanges; without this, this PR wouldn't have run any testsLocally, 4 processes took
Core.Testsfrom about 69s to 28–36s,Api.IntegrationTestsfrom 42s to 18–22s andSupportUi.Testsfrom 69s to 35–42s. CI's gain will be smaller, since setup and build take 100–150s per job. The last comparable run took 317s in total.🤖 Generated with Claude Code