From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Cc: Alex Henrie <alexhenrie24@gmail.com>,
Elijah Newren <newren@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] pull: abort by default if fast-forwarding is impossible
Date: Mon, 28 Jun 2021 12:39:38 -0500 [thread overview]
Message-ID: <60da095a5ce4_1a78f20847@natae.notmuch> (raw)
In-Reply-To: <87k0megtlo.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
>
> On Sun, Jun 27 2021, Felipe Contreras wrote:
> > Personally I prefer to run prove instead, because the output is less
> > verbose, and there's a nice summary at the end:
> >
> > prove t[0-9][0-9][0-9][0-9]-*.sh
>
> I also like "prove" better (well, I added the support for it, so
> ...). It's generally better to use e.g.:
>
> make test DEFAULT_TEST_TARGET=prove GIT_PROVE_OPTS="--jobs $(nproc)"
Or just add "-j$(nproc)" to ~/.proverc so you don't need to specify
GIT_PROVE_OPTS every time.
> Since we do some basic checking via the Makefile that effectively form a
> part of our tests.
>
> FWIW for your one-liner it can be just:
>
> prove t[0-9]*.sh
>
> Alex: You might also find that if you specify --root as the path to a
> ramdisk the tests are much faster, e.g. on my Linux boxes I set
> --root=/run/user/`id -u`/git.
Or TEST_OUTPUT_DIRECTORY=/tmp/git.
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-28 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 0:08 [PATCH] pull: abort by default if fast-forwarding is impossible Alex Henrie
2021-06-27 1:34 ` Elijah Newren
2021-06-27 4:16 ` Felipe Contreras
2021-06-27 7:49 ` Elijah Newren
2021-06-27 16:46 ` Felipe Contreras
2021-06-27 19:54 ` Alex Henrie
2021-06-27 21:29 ` Felipe Contreras
2021-06-28 10:31 ` Ævar Arnfjörð Bjarmason
2021-06-28 17:39 ` Felipe Contreras [this message]
2021-06-27 4:12 ` Felipe Contreras
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=60da095a5ce4_1a78f20847@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=alexhenrie24@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
/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).