From: Andrei Rybak <rybak.a.v@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Øystein Walle" <oystwa@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH v2 4/6] t1450: don't create unused files
Date: Fri, 7 Apr 2023 00:19:03 +0200 [thread overview]
Message-ID: <35bc2dc5-d5cb-3492-ff94-41b93b7563d4@gmail.com> (raw)
In-Reply-To: <230406.86lej5tn8c.gmgdl@evledraar.gmail.com>
On 06/04/2023 10:41, Ævar Arnfjörð Bjarmason wrote:
>
> On Tue, Apr 04 2023, Andrei Rybak wrote:
>> ---
>> t/ | 5 +----
>> 1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> diff --git a/t/t1450-fsck.sh b/t/t1450-fsck.sh
>> index bca46378b2..8c442adb1a 100755
>> --- a/t/t1450-fsck.sh
>> +++ b/t/t1450-fsck.sh
>> @@ -989,10 +989,7 @@ test_expect_success 'fsck error and recovery on invalid object type' '
>>
>> garbage_blob=$(git hash-object --stdin -w -t garbage --literally </dev/null) &&
>>
>> - cat >err.expect <<-\EOF &&
>> - fatal: invalid object type
>> - EOF
>> - test_must_fail git fsck >out 2>err &&
>> + test_must_fail git fsck 2>err &&
>> grep -e "^error" -e "^fatal" err >errors &&
>> test_line_count = 1 errors &&
>> grep "$garbage_blob: object is of unknown type '"'"'garbage'"'"':" err
>
> ...but ditto my review on other patches, this just seems like a mistake
> of mine, i.e. if I add the "test_must_be_empty out" the test passes.
>
> So isn't the answer here that my 31deb28f5e had an unintentional
> regression, and we should bring the assertion back? Its commit message
> says nothing about wanting to stop asserting stdout.
>
> Maybe there was a reason I'm missing for why I remved it, it's since
> been paged out of my wetware, but looking at it briefly now it just
> seems like an unintentional bug / loss of test coverage that we should
> fix.
Tests in t1450-fsck.sh that do enforce empty standard output do it mostly
via ">../actual 2>&1" and then a "test_must_be_empty actual".
For 'fsck error and recovery on invalid object type', the question is:
is having this assertion useful for a developer using this test? The test
is about invalid object types and what error messages "git fsck" prints
about them. The test creates a fresh repository for it:
> git init --bare garbage-type &&
Is it useful to a developer working on this part of "git fsck" to have
a "reminder" that no dangling objects should be found in such a fresh
repository? Speaking of which, should there be such a test:
test_expect_success 'fresh repository has no dangling objects' '
git init fresh &&
git -C fresh fsck >out
test_must_be_empty out
'
? Maybe even in t0001-init.sh?
next prev parent reply other threads:[~2023-04-06 22:19 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 21:28 [PATCH v1 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 1/6] t0300: don't create unused file Andrei Rybak
2023-04-02 1:30 ` Eric Sunshine
2023-04-01 21:28 ` [PATCH v1 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 3/6] t1300: don't create unused files Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 4/6] t1450: " Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 5/6] t1502: " Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 6/6] t2019: " Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 1/6] t0300: don't create unused file Andrei Rybak
2023-04-06 8:34 ` Ævar Arnfjörð Bjarmason
2023-04-06 21:01 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 3/6] t1300: don't create unused files Andrei Rybak
2023-04-06 8:38 ` Ævar Arnfjörð Bjarmason
2023-04-06 21:30 ` Andrei Rybak
2023-04-06 21:35 ` git config tests for "'git config ignores pairs ..." (was Re: [PATCH v2 3/6] t1300: don't create unused files) Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 0/2] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 1/2] t1300: drop duplicate test Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 2/2] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-14 13:28 ` Andrei Rybak
2023-04-18 17:50 ` [PATCH v2 0/3] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-18 17:50 ` [PATCH v2 1/3] t1300: drop duplicate test Andrei Rybak
2023-04-18 18:37 ` Junio C Hamano
2023-04-18 17:50 ` [PATCH v2 2/3] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-18 18:39 ` Junio C Hamano
2023-04-18 17:50 ` [RFC PATCH v2 3/3] t1300: add tests for missing keys Andrei Rybak
2023-04-18 19:31 ` Junio C Hamano
2023-04-18 17:53 ` [PATCH v2 0/3] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 " Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 1/3] t1300: drop duplicate test Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 2/3] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 3/3] t1300: add tests for missing keys Andrei Rybak
2023-05-01 22:02 ` [PATCH v3 0/3] git config tests for "'git config ignores pairs ..." Junio C Hamano
2023-05-02 19:58 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 4/6] t1450: don't create unused files Andrei Rybak
2023-04-06 8:41 ` Ævar Arnfjörð Bjarmason
2023-04-06 22:19 ` Andrei Rybak [this message]
2023-04-03 22:33 ` [PATCH v2 5/6] t1502: " Andrei Rybak
2023-04-06 8:15 ` Øystein Walle
2023-04-06 8:47 ` Ævar Arnfjörð Bjarmason
2023-04-06 19:51 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 6/6] t2019: " Andrei Rybak
2023-04-06 8:44 ` Ævar Arnfjörð Bjarmason
2023-04-07 2:19 ` Andrei Rybak
2023-04-08 20:54 ` [PATCH] t2024: fix loose/strict local base branch DWIM test Andrei Rybak
2023-04-10 17:37 ` Junio C Hamano
2023-04-17 19:10 ` [PATCH v3 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 1/6] t0300: don't create unused file Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 3/6] t1300: don't create unused files Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 4/6] t1450: " Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 5/6] t1502: " Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 6/6] t2019: " Andrei Rybak
2023-05-01 21:52 ` [PATCH v3 0/6] t: fix unused files, part 2 Junio C Hamano
2023-05-02 21:03 ` Andrei Rybak
2023-05-03 4:11 ` Elijah Newren
2023-05-03 15:54 ` 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=35bc2dc5-d5cb-3492-ff94-41b93b7563d4@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=oystwa@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).