From: Johannes Sixt <j6t@kdbg.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Ramsay Jones <ramsay@ramsayjones.plus.com>
Subject: Re: [PATCH] t0050: remove the unused $test_case variable
Date: Wed, 7 Feb 2018 19:42:46 +0100 [thread overview]
Message-ID: <a8bc404e-fca8-6d64-21c4-df6d6879bee7@kdbg.org> (raw)
In-Reply-To: <87fu6dz0h6.fsf@evledraar.gmail.com>
Am 07.02.2018 um 09:07 schrieb Ævar Arnfjörð Bjarmason:
>
> On Wed, Feb 07 2018, Johannes Sixt jotted:
>
>> Am 07.02.2018 um 00:13 schrieb Ævar Arnfjörð Bjarmason:
>>> The $test_case variable hasn't been used since
>>> decd3c0c28 ("t0050-*.sh: mark the rename (case change) test as
>>> passing", 2014-11-28) when its last user went away.
>>>
>>> Let's remove the "say" as well, since it's obvious from subsequent
>>> output that we're testing on a case sensitive filesystem.
>>
>> Am I misunderstanding the message? I think it reports properties of
>> the test environment. And the tests do run on case-insensitive
>> filesystems. IMO, the message should be kept.
>
> It's obvious from subsequent output whether the FS is case sensitive or
> not, so I thought it was redundant to keep this report at the top since
> we didn't have the variable setting anymore.
There are test cases that do different things depending on whether the
CASE_INSENSITIVE_FS prerequisite is set. I think it was the intent to
report whether it is set and not whether one or the other value of the
(now unused) variable is used somewhere.
BTW, the message texts do not show which variant is taken (these are
without your patch):
On Windows:
t>sh t0050-filesystem.sh
will test on a case insensitive filesystem
will test on a filesystem lacking symbolic links
ok 1 - detection of case insensitive filesystem during repo init
ok 2 - detection of filesystem w/o symlink support during repo init
ok 3 - setup case tests
ok 4 - rename (case change)
ok 5 - merge (case change)
not ok 6 - add (with different case) # TODO known breakage
ok 7 - setup unicode normalization tests
ok 8 - rename (silent unicode normalization)
ok 9 - merge (silent unicode normalization)
# still have 1 known breakage(s)
# passed all remaining 8 test(s)
1..9
On Linux:
t@master:1002> ./t0050-filesystem.sh
ok 1 - detection of case insensitive filesystem during repo init
ok 2 - detection of filesystem w/o symlink support during repo init
ok 3 - setup case tests
ok 4 - rename (case change)
ok 5 - merge (case change)
ok 6 # skip add (with different case) (missing CASE_INSENSITIVE_FS)
ok 7 - setup unicode normalization tests
ok 8 - rename (silent unicode normalization)
ok 9 - merge (silent unicode normalization)
# passed all 9 test(s)
1..9
I'd even argue that there should be messages on Linux, too.
-- Hannes
next prev parent reply other threads:[~2018-02-07 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 23:13 [PATCH] t0050: remove the unused $test_case variable Ævar Arnfjörð Bjarmason
2018-02-07 7:20 ` Johannes Sixt
2018-02-07 8:07 ` Ævar Arnfjörð Bjarmason
2018-02-07 18:42 ` Johannes Sixt [this message]
2018-02-07 19:08 ` Ævar Arnfjörð Bjarmason
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=a8bc404e-fca8-6d64-21c4-df6d6879bee7@kdbg.org \
--to=j6t@kdbg.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsayjones.plus.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).