From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Fix the speed of the CI (Visual Studio) tests
Date: Sun, 20 Oct 2019 20:39:28 +0000 [thread overview]
Message-ID: <pull.410.git.1571603970.gitgitgadget@gmail.com> (raw)
I made a mistake when converting the make/prove-based test job to a
test-tool run-command testsuite one: I lost the parallelization, resulting
in way slower CI runs.
Also, I forgot to build with DEVELOPER=1, i.e. with stricter compile flags.
This pair of patches fixes both issues.
Johannes Schindelin (2):
ci(visual-studio): use strict compile flags, and optimization
ci(visual-studio): actually run the tests in parallel
azure-pipelines.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: d966095db01190a2196e31195ea6fa0c722aa732
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-410%2Fdscho%2Faccelerate-ci-vs-test-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-410/dscho/accelerate-ci-vs-test-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/410
--
gitgitgadget
next reply other threads:[~2019-10-20 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 20:39 Johannes Schindelin via GitGitGadget [this message]
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
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=pull.410.git.1571603970.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.