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

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

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Oct 20, 2019, 21:23 UTC
Message-ID
<CAPig+cRZ07OGB4kKO=fozh8fRnCLa0ZrxuUFD3By9c62DZe9BA@mail.gmail.com>
In-Reply-To
<e3343d174008a3fe21c159c197913ce749e21589.1571603970.git.gitgitgadget@gmail.com>

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/
Show 9 quoted lines
> `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>
Previous: Johannes Schindelin via GitGitGadgetNext: Johannes Schindelin via GitGitGadget
Message 3 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.