git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/2] ci(visual-studio): actually run the tests in parallel
Date: Sun, 20 Oct 2019 17:23:23 -0400	[thread overview]
Message-ID: <CAPig+cRZ07OGB4kKO=fozh8fRnCLa0ZrxuUFD3By9c62DZe9BA@mail.gmail.com> (raw)
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/

> `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>

  reply	other threads:[~2019-10-20 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 20:39 [PATCH 0/2] Fix the speed of the CI (Visual Studio) tests Johannes Schindelin via GitGitGadget
2019-10-20 20:39 ` [PATCH 1/2] ci(visual-studio): use strict compile flags, and optimization Johannes Schindelin via GitGitGadget
2019-10-20 20:39 ` [PATCH 2/2] ci(visual-studio): actually run the tests in parallel Johannes Schindelin via GitGitGadget
2019-10-20 21:23   ` Eric Sunshine [this message]
2019-10-21 19:59 ` [PATCH v2 0/2] Fix the speed of the CI (Visual Studio) tests Johannes Schindelin via GitGitGadget
2019-10-21 19:59   ` [PATCH v2 1/2] ci(visual-studio): use strict compile flags, and optimization Johannes Schindelin via GitGitGadget
2019-10-21 19:59   ` [PATCH v2 2/2] ci(visual-studio): actually run the tests in parallel Johannes Schindelin via GitGitGadget
2019-10-23  2:06   ` [PATCH v2 0/2] Fix the speed of the CI (Visual Studio) tests Junio C Hamano
2019-10-24 23:23     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPig+cRZ07OGB4kKO=fozh8fRnCLa0ZrxuUFD3By9c62DZe9BA@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).