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

RE: [PATCH] t1800: correct test to handle Cygwin

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Sep 7, 2022, 20:57 UTC
Message-ID
<001301d8c2fc$78dc4bc0$6a94e340$@nexbridge.com>
In-Reply-To
<xmqqy1uusyez.fsf@gitster.g>
On September 7, 2022 4:49 PM, Junio C Hamano wrote:
Show 31 quoted lines
>Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>>> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad
>shebang' '
>>>  	# TODO: We should emit the same (or at least a more similar)
>>>  	# error on Windows and !Windows. See the OS-specific code in
>>>  	# start_command()
>>> -	if test_have_prereq !WINDOWS
>>> +	if test_have_prereq !MINGW
>>
>> ... this to be `test_have_prereq !WINDOWS || test_have_prereq CYGWIN`
>> instead.
>
>My understanding is that there are CYGWIN and MINGW prereqs that are
>mutually exclusive (if you are on MINGW you cannot be on CYGWIN and vice
>versa), and WINDOWS is a short-hand for "we are either on MINGW or CYGWIN",
>and I am not sure if it clarifies anything to rewrite "we do not want to be on
>MINGW to run these tests" to "anything non Windows is fine, by the way,
>CYGWIN is also OK".
>
>If we are planning to add another variant that falls into umbrella WINDOWS that is
>not CYGWIN, and that new variant falls short of the requirement of the tests in
>this script just like MINGW does, then the suggested rewrite does make quite a lot
>of sense.  There would be not just two but more variants in Windows family, and if
>Cygwin is the odd man out, then the rewritten one would convey that more
>clearly.  But with only two, as long as everybody understands what MINGW is, I
>think "this part does not work on MINGW" is more concise and clear.
>
>As Đoàn Trần Công Danh pointed out, the TODO: comment may need to be
>updated.  For future-proofing, perhaps "a more similar) error on all platforms."
>would be appropriate.
I think this is the same as I reported under [BUG] t1800: Fails for error text comparison, which somehow Outlook associated with a different thread. NonStop has the same issue with error messages not being consistent across platforms.
-Randall
Previous: Junio C HamanoNext: Adam Dinwoodie
Message 6 of 10 in “t1800: correct test to handle Cygwin”
  1. t1800: correct test to handle CygwinAdam Dinwoodie, Sep 1, 2022
  2. Junio C HamanoSep 1, 2022
  3. Đoàn Trần Công DanhSep 2, 2022
  4. Johannes SchindelinSep 2, 2022
  5. Junio C HamanoSep 7, 2022
  6. rsbecker@nexbridge.comSep 7, 2022
  7. Adam DinwoodieSep 13, 2022
  8. Junio C HamanoSep 13, 2022
  9. t1800: correct test to handle CygwinAdam Dinwoodie, Sep 15, 2022
  10. rsbecker@nexbridge.comSep 15, 2022

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.