From: Andrei Rybak <rybak.a.v@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: [BUG] range expressions in GIT_SKIP_TESTS are broken in master (was [BUG] question mark in GIT_SKIP_TESTS is broken in master)
Date: Wed, 16 Jun 2021 01:28:33 +0200 [thread overview]
Message-ID: <6980e906-8076-1436-ecdb-6775eff55d39@gmail.com> (raw)
In-Reply-To: <1d003cac-83fa-0b63-f60e-55513ac45cf9@gmail.com>
On 15/06/2021 22:55, Andrei Rybak wrote:
> Hi,
>
> I've taken an example of how to use GIT_SKIP_TESTS directly from
> t/README:
>
> $ GIT_SKIP_TESTS='t[0-4]??? t91?? t9200.8' make
>
> and noticed that t0000 is still being run. I've written a script to
> bisect the issue:
>
>
> #/bin/sh
>
> (
> cd t
> GIT_SKIP_TESTS='t[0-4]??? t91?? t9200.8' make | \
> head | grep 'SKIP skip all tests in t0000'
> )
>
>
> and it bisected to edc23840b0 (test-lib: bring $remove_trash out of
> retirement, 2021-05-10) which was merged to master in 2019256717 ("Merge
> branch 'ab/test-lib-updates'", 2021-06-14).
>
> Note, that spelling out the tests number in full works, i.e.
>
> $ GIT_SKIP_TESTS=t0000 make
>
> won't run t0000.
I sent this originally with incorrect subject. Question marks, e.g.
$ GIT_SKIP_TESTS='t000?' make
work. It is the range expressions, like [0-9] that are broken:
$ GIT_SKIP_TESTS='t[0-9]000' make
next prev parent reply other threads:[~2021-06-15 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 20:55 [BUG] question mark in GIT_SKIP_TESTS is broken in master Andrei Rybak
2021-06-15 23:28 ` Andrei Rybak [this message]
2021-06-16 3:28 ` [BUG] range expressions in GIT_SKIP_TESTS are broken in master (was [BUG] question mark in GIT_SKIP_TESTS is broken in master) Junio C Hamano
2021-06-16 4:12 ` Junio C Hamano
2021-06-16 8:29 ` Jeff King
2021-06-16 9:19 ` Junio C Hamano
2021-06-16 8:24 ` [PATCH] test-lib: fix "$remove_trash" regression and match_pattern_list() bugs Ævar Arnfjörð Bjarmason
2021-06-16 8:36 ` Jeff King
2021-06-16 9:22 ` Junio C Hamano
2021-06-16 10:23 ` Jeff King
2021-06-16 10:24 ` Jeff King
2021-06-16 11:38 ` Ævar Arnfjörð Bjarmason
2021-06-16 11:50 ` Jeff King
2021-06-17 0:29 ` Junio C Hamano
2021-06-16 9:49 ` Ævar Arnfjörð Bjarmason
2021-06-16 11:43 ` Jeff King
2021-06-17 0:36 ` Junio C Hamano
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=6980e906-8076-1436-ecdb-6775eff55d39@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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).