diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-10-21 19:59:58 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-10-23 11:02:59 +0900 |
commit | 399c23c046fc40cc3637d7e3688dcbe31b27a030 (patch) | |
tree | ebd5a0c3bf3c3812985742554c2d3649858eb177 /git-merge-resolve.sh | |
parent | ci(visual-studio): use strict compile flags, and optimization (diff) | |
download | tgif-399c23c046fc40cc3637d7e3688dcbe31b27a030.tar.xz |
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>
Diffstat (limited to 'git-merge-resolve.sh')
0 files changed, 0 insertions, 0 deletions