summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2019-10-21 19:59:58 (GMT)
committerJunio C Hamano <gitster@pobox.com>2019-10-23 02:02:59 (GMT)
commit399c23c046fc40cc3637d7e3688dcbe31b27a030 (patch)
treeebd5a0c3bf3c3812985742554c2d3649858eb177
parent711cd6d15cf9394d1aa0f78c68a7a39b3bb23509 (diff)
downloadgit-399c23c046fc40cc3637d7e3688dcbe31b27a030.zip
git-399c23c046fc40cc3637d7e3688dcbe31b27a030.tar.gz
git-399c23c046fc40cc3637d7e3688dcbe31b27a030.tar.bz2
ci(visual-studio): actually run the tests in parallel
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> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--azure-pipelines.yml2
1 files changed, 1 insertions, 1 deletions
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 0c28e00..17a942e 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)
"@