Message ID | e3343d174008a3fe21c159c197913ce749e21589.1571603970.git.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | Fix the speed of the CI (Visual Studio) tests | expand |
On Sun, Oct 20, 2019 at 4:39 PM Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote: > [...] > 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` nore with support for s/nore/nor/ > `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>
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) "@