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

Re: [PATCH v2 2/2] t9813: avoid using pipes

From
Pranit Bauva <pranit.bauva@gmail.com>
Date
Jan 3, 2017, 19:44 UTC
Message-ID
<CAFZEwPPfE_WSn2QbmER+5mkaC8RnVDs5gsSJE+Y0v-CfYaZB2w@mail.gmail.com>
In-Reply-To
<CAGZ79kZRFLzD7wcAnFvke9vBxxTAgE7=Ud7F_O95EfkWqz=LJw@mail.gmail.com>
Hey Stefan,
On Tue, Jan 3, 2017 at 11:28 PM, Stefan Beller <sbeller@google.com> wrote:
Show 14 quoted lines
> On Mon, Jan 2, 2017 at 10:45 AM, Pranit Bauva <pranit.bauva@gmail.com> wrote:
>> The exit code of the upstream in a pipe is ignored thus we should avoid
>> using it.
>
> for commands under test, i.e. git things. Other parts can be piped if that makes
> the test easier. Though I guess that can be guessed by the reader as well,
> as you only convert git commands on upstream pipes.
>
>> By writing out the output of the git command to a file, we can
>> test the exit codes of both the commands.
>>
>> Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com>
>
> Thanks for taking ownership of this issue as well. :)
Welcome! ;)
Show 24 quoted lines
>> ---
>>  t/t9813-git-p4-preserve-users.sh | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/t/t9813-git-p4-preserve-users.sh b/t/t9813-git-p4-preserve-users.sh
>> index 798bf2b67..9d7550ff3 100755
>> --- a/t/t9813-git-p4-preserve-users.sh
>> +++ b/t/t9813-git-p4-preserve-users.sh
>> @@ -118,12 +118,12 @@ test_expect_success 'not preserving user with mixed authorship' '
>>                 make_change_by_user usernamefile3 Derek derek@example.com &&
>>                 P4EDITOR=cat P4USER=alice P4PASSWD=secret &&
>>                 export P4EDITOR P4USER P4PASSWD &&
>> -               git p4 commit |\
>> -               grep "git author derek@example.com does not match" &&
>> +               git p4 commit >actual 2>&1 &&
>
> Why do we need to pipe 2>&1 here?
> Originally the piping only fed the stdout to grep, so this patch changes the
> test? Maybe
>
>     2>actual.err &&
>     test_must_be_empty actual.err
>
> instead?

I tried this out but it seems that travis-ci build fails[1]. And I don't have p4 on my machine to test what's happening actually. But I just pushed out a few thing modifications to travis and it seems that actual.err isn't really empty for some reason. So I think, I just leave it as,

git p4 commit >actual && grep "git author derek@example.com does not match" actual &&

What do you think?
[1]: https://travis-ci.org/pranitbauva1997/git/jobs/188633734

Regards, Pranit Bauva

Previous: Stefan BellerNext: Stefan Beller
Message 11 of 21 in “don't use test_must_fail with grep”
  1. don't use test_must_fail with grepPranit Bauva, Dec 31, 2016
  2. Luke DiamandJan 1, 2017
  3. Johannes SixtJan 1, 2017
  4. Luke DiamandJan 1, 2017
  5. Pranit BauvaJan 2, 2017
  6. Junio C HamanoJan 7, 2017
  7. Pranit BauvaJan 8, 2017
  8. 1/2 don't use test_must_fail with grepPranit Bauva, Jan 2, 2017
  9. 2/2 t9813: avoid using pipesPranit Bauva, Jan 2, 2017
  10. Stefan BellerJan 3, 2017
  11. Pranit BauvaJan 3, 2017
  12. Stefan BellerJan 3, 2017
  13. 1/2 don't use test_must_fail with grepPranit Bauva, Jan 3, 2017
  14. 2/2 t9813: avoid using pipesPranit Bauva, Jan 3, 2017
  15. Luke DiamandJan 4, 2017
  16. Pranit BauvaJan 4, 2017
  17. 1/2 don't use test_must_fail with grepPranit Bauva, Jan 8, 2017
  18. 2/2 t9813: avoid using pipesPranit Bauva, Jan 8, 2017
  19. Luke DiamandJan 9, 2017
  20. Junio C HamanoJan 9, 2017
  21. Stefan BellerJan 3, 2017

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.