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

Re: [PATCH] t/t3700: convert two uses of negation operator '!' to use test_must_fail

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Jul 20, 2010, 18:25 UTC
Message-ID
<AANLkTilf4Z0FI9jkREJx6EJHv1OH1J4XZOQmE1rR_Mu4@mail.gmail.com>
In-Reply-To
<fVE942wHC3SFihkQG8AthPTKiTZtYJ9zmR2TT7F5OlkGD4IA9xPcMA@cipher.nrlssc.navy.mil>
On Tue, Jul 20, 2010 at 16:32, Brandon Casey <casey@nrlssc.navy.mil> wrote:
Show 34 quoted lines
>>> This was noticed because the second use of '!' does not include a space
>>> between the '!' and the opening parens.  Ksh interprets this as follows:
>>>
>>>   !(pattern-list)
>>>      Matches anything except one of the given patterns.
>>>
>>> Ksh performs a file glob using the pattern-list and then tries to execute
>>> the first file in the list.  If a space is added between the '!' and the
>>> open parens, then Ksh will not interpret it as a pattern list, but in this
>>> case, it is preferred to use test_must_fail, so lets do so.
>>
>> Isn't this a completely seperate thing? Was this test really the only
>> bit in the test suite that did "!foo" instead of "! foo" ?
>
> This was the only instance of "!()" that was failing for me.  I didn't
> look before, but now that I have, there is another instance of "!()" in
> t5541 that should be fixed.  t5541 hasn't caused a problem for me because
> GIT_TEST_HTTPD must be set in order to enable it, and I haven't done so.
>
>> Does the test pass for you if you just:
>
> Yes.
>
>>     @@ -281,7 +281,7 @@ add 'track-this'
>>      EOF
>>
>>      test_expect_success 'git add --dry-run --ignore-missing of
>> non-existing file' '
>>     -       !(git add --dry-run --ignore-missing track-this
>> ignored-file >actual 2>&1) &&
>>     +       ! (git add --dry-run --ignore-missing track-this
>> ignored-file >actual 2>&1) &&
>>            test_cmp expect actual
>>      '

A seperate patch to clean up those two + doc patch to the "Do's, don'ts & things to keep in mind" section in t/README would be really useful IMO. I had no idea that "!cmd" was an issue no ksh.

Previous: Ævar Arnfjörð BjarmasonNext: Jonathan Nieder
Message 37 of 40 in “t/t3700: convert two uses of negation operator '!' to use test_must_fail”
  1. t/t3700: convert two uses of negation operator '!' to use test_must_failBrandon Casey, Jul 20, 2010
  2. Ævar Arnfjörð BjarmasonJul 20, 2010
  3. Brandon CaseyJul 20, 2010
  4. Jared HanceJul 20, 2010
  5. t/README: clarify test_must_fail descriptionBrandon Casey, Jul 20, 2010
  6. Junio C HamanoJul 20, 2010
  7. Ævar Arnfjörð BjarmasonJul 20, 2010
  8. Jared HanceJul 20, 2010
  9. Convert "! git" to "test_must_fail" git.Jared Hance, Jul 20, 2010
  10. Brandon CaseyJul 20, 2010
  11. Jonathan NiederJul 20, 2010
  12. Brandon CaseyJul 20, 2010
  13. Convert "! git" to "test_must_fail git"Jared Hance, Jul 20, 2010
  14. Junio C HamanoJul 20, 2010
  15. Ævar Arnfjörð BjarmasonJul 20, 2010
  16. Jonathan NiederJul 20, 2010
  17. Ævar Arnfjörð BjarmasonJul 20, 2010
  18. Brandon CaseyJul 20, 2010
  19. Ævar Arnfjörð BjarmasonJul 20, 2010
  20. t/: work around one-shot variable assignment with test_must_failBrandon Casey, Jul 20, 2010
  21. Erick MattosJul 20, 2010
  22. Brandon CaseyJul 21, 2010
  23. Erick MattosJul 22, 2010
  24. Ævar Arnfjörð BjarmasonJul 20, 2010
  25. Ævar Arnfjörð BjarmasonJul 20, 2010
  26. Jonathan NiederJul 21, 2010
  27. Ævar Arnfjörð BjarmasonJul 21, 2010
  28. Jonathan NiederJul 21, 2010
  29. Ævar Arnfjörð BjarmasonJul 21, 2010
  30. git name-rev for fun and profit (Re: [PATCH] t/: work around one-shot variable assignment with test_must_fail)Jonathan Nieder, Jul 21, 2010
  31. Ævar Arnfjörð BjarmasonJul 21, 2010
  32. Junio C HamanoJul 21, 2010
  33. Erick MattosJul 22, 2010
  34. Brandon CaseyJul 22, 2010
  35. Brandon CaseyJul 20, 2010
  36. Ævar Arnfjörð BjarmasonJul 20, 2010
  37. Ævar Arnfjörð BjarmasonJul 20, 2010
  38. gitweb: clarify search results page when no matching commit foundJonathan Nieder, Jul 21, 2010
  39. Jakub NarebskiJul 21, 2010
  40. gitweb: clarify search results page when no matching commit foundJonathan Nieder, Jul 21, 2010

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.