git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] tests: drop use of 'tee' that hides exit status

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 13, 2024, 17:23 UTC
Message-ID
<xmqqcymc5oc5.fsf@gitster.g>
In-Reply-To
<f5d0510c-d455-5e80-08b7-e08c81df4adb@gmx.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 20 quoted lines
> Hi Junio,
>
> On Thu, 8 Aug 2024, Junio C Hamano wrote:
>
>> diff --git c/t/t1001-read-tree-m-2way.sh w/t/t1001-read-tree-m-2way.sh
>> index 88c524f655..48a1550371 100755
>> --- c/t/t1001-read-tree-m-2way.sh
>> +++ w/t/t1001-read-tree-m-2way.sh
>> @@ -397,7 +397,7 @@ test_expect_success 'a/b vs a, plus c/d case setup.' '
>>
>>  test_expect_success 'a/b vs a, plus c/d case test.' '
>>  	read_tree_u_must_succeed -u -m "$treeH" "$treeM" &&
>> -	git ls-files --stage | tee >treeMcheck.out &&
>> +	git ls-files --stage >treeMcheck.out &&
>
> While this obviously fixes the bug where the test case was incorrectly
> allowed to continue after a failing `git ls-files --stage` call, I will
> note that I interpret the intention of the `| tee` as showing the output
> in the logs in addition to redirecting it to a file for the benefit of
> additional checks in the same test case.
If we really want to do that, we'd do
    git ls-files --stage >treeMcheck.out &&
    cat treeMcheck.out &&

instead. You wouldn't lose the exit status, and the output would show the contents just like "tee" would.

We however tend to also remove a leftover debugging "cat", so the "cat" is likely to be removed during such a clean-up.

> So, what to do here? I don't really know. The easiest option that most
> other people would likely be happy with would be to go with the `| tee`
> dropping.

As long as we treat the CI as a "batch" environment, the postmortem tarball of the trash directory is probably the best we can do I can think of.

Previous: Jeff King
Message 6 of 6 in “tests: drop use of 'tee' that hides exit status”
  1. tests: drop use of 'tee' that hides exit statusJunio C Hamano, Aug 8, 2024
  2. Rubén JustoAug 9, 2024
  3. Junio C HamanoAug 9, 2024
  4. Johannes SchindelinAug 13, 2024
  5. Jeff KingAug 13, 2024
  6. Junio C HamanoAug 13, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.