git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 2/2] ci(visual-studio): actually run the tests in parallel

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 21, 2019, 19:59 UTC
Message-ID
<07749ab720af05b3f666e325e9bc3c4c5d8196e5.1571687999.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.410.v2.git.1571687999.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>

Originally, the CI/PR builds that build and test using Visual Studio were implemented imitating `linux-clang`, i.e. still using the `Makefile`-based build infrastructure.

Later (but still before the patches made their way into git.git's `master`), however, this was changed to generate Visual Studio project files and build the binaries using `MSBuild`, as this reflects more accurately how Visual Studio users would want to build Git (internally, Visual Studio uses `MSBuild`, or at least something very similar).

During that transition, we needed to implement a new way to run the test suite in parallel, as Visual Studio users typically will only have a Git Bash available (which does not ship with `make` nor with support for `prove`): we simply implemented a new test helper to run the test suite.

This helper even knows how to run the tests in parallel, but due to a mistake on this developer's part, it was never turned on in the CI/PR builds. This results in 2x-3x longer run times of the test phase.

Let's use the `--jobs=10` option to fix this.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
 azure-pipelines.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 457c6fee31..af2a5ea484 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -255,7 +255,7 @@ jobs:
 
         cd t &&
         PATH=\"`$PWD/helper:`$PATH\" &&
-        test-tool.exe run-command testsuite -V -x --write-junit-xml \
+        test-tool.exe run-command testsuite --jobs=10 -V -x --write-junit-xml \
                 `$(test-tool.exe path-utils slice-tests \
                         `$SYSTEM_JOBPOSITIONINPHASE `$SYSTEM_TOTALJOBSINPHASE t[0-9]*.sh)
       "@
-- 
gitgitgadget
Previous: Johannes Schindelin via GitGitGadgetNext: Junio C Hamano
Message 7 of 9 in “Fix the speed of the CI (Visual Studio) tests”
  1. 0/2 Fix the speed of the CI (Visual Studio) testsJohannes Schindelin via GitGitGadget, Oct 20, 2019
  2. 2/2 ci(visual-studio): actually run the tests in parallelJohannes Schindelin via GitGitGadget, Oct 20, 2019
  3. Eric SunshineOct 20, 2019
  4. 1/2 ci(visual-studio): use strict compile flags, and optimizationJohannes Schindelin via GitGitGadget, Oct 20, 2019
  5. 0/2 Fix the speed of the CI (Visual Studio) testsJohannes Schindelin via GitGitGadget, Oct 21, 2019
  6. 1/2 ci(visual-studio): use strict compile flags, and optimizationJohannes Schindelin via GitGitGadget, Oct 21, 2019
  7. 2/2 ci(visual-studio): actually run the tests in parallelJohannes Schindelin via GitGitGadget, Oct 21, 2019
  8. Junio C HamanoOct 23, 2019
  9. Johannes SchindelinOct 24, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.