From fa3cf59494a192f97ce14dc450e1e1edc5e8ec35 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 13 Mar 2026 14:03:38 +0000 Subject: [PATCH 1/2] perf: parallelise test project builds when running tests Previously, buildProject was invoked sequentially via mapExecuteForAll for each project in the run request. Switch to executeWithMaxParallel (capped at maxParallelTestProjects = 3) so builds run concurrently, matching the pattern already used for the actual test-execution step. This is a companion change to the parallel-builds improvement in refreshTestList (PR #2142). The benefit is most visible when the user chooses 'Run All Tests' across a solution with several test projects. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- src/Components/TestExplorer.fs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Components/TestExplorer.fs b/src/Components/TestExplorer.fs index a6bcafb7..a27bf2cf 100644 --- a/src/Components/TestExplorer.fs +++ b/src/Components/TestExplorer.fs @@ -1984,9 +1984,9 @@ module Interactions = let! buildResults = projectRunRequests |> List.ofArray - |> Promise.mapExecuteForAll (buildProject testRun) + |> Promise.executeWithMaxParallel maxParallelTestProjects (buildProject testRun) - let successfullyBuiltRequests = buildResults |> List.choose id + let successfullyBuiltRequests = buildResults |> Array.choose id |> List.ofArray if useLegacyDotnetCliIntegration then let! _ = From 1f2b7e1f6ed2844fc6424f239e8903c6aedeb9c6 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 13 Mar 2026 14:10:09 +0000 Subject: [PATCH 2/2] ci: trigger checks