From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: Vladimir Marek <Vladimir.Marek@oracle.com>, git@vger.kernel.org
Subject: Re: Fix for failing tests on Solaris
Date: Fri, 29 Apr 2022 09:48:50 -0700 [thread overview]
Message-ID: <xmqqr15fdedp.fsf@gitster.g> (raw)
In-Reply-To: <20220429160913.wogvmyxosctdlosz@carlos-mbp.lan> ("Carlo Marcelo Arenas Belón"'s message of "Fri, 29 Apr 2022 09:09:13 -0700")
Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:
>> --- git-2.35.1/config.mak.uname
>> +++ git-2.35.1/config.mak.uname
>> @@ -162,7 +162,7 @@ ifeq ($(uname_S),SunOS)
>> NEEDS_SOCKET = YesPlease
>> NEEDS_NSL = YesPlease
>> SHELL_PATH = /bin/bash
>> - SANE_TOOL_PATH = /usr/xpg6/bin:/usr/xpg4/bin
>> + SANE_TOOL_PATH = /usr/gnu/bin
>
> I haven't used Solaris for a while (since around OpenSolaris Indiana
> development stopped), but wouldn't this break in Solaris 10 and older?
>
>> Makes all tests but t7812 pass successfully. t7812 fails on locales and
>> utf-8 which do behave differently in Solaris.
>
> And additional fix for that (since you seem to have access to a fresh
> Solaris 11.4 installation at least), would be forthcomming.
>
> Wondering also if there is a way to plug one of those from Oracle Cloud
> through a GitHub actions so we could prevent future issues by including
> Solaris in our CI runs.
I do not think we want to take this patch until we know how exactly
the tests failing for Vladimir fail without GNUism, which we do not
want to rely on. If a test by mistake used "sed -i -e '<script>'"
GNUism which /usr/xpg[46]/bin/sed does not support, for example, we
want to know about it, so that we can move away from such a use of
GNUism.
Thanks.
prev parent reply other threads:[~2022-04-29 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 6:23 Fix for failing tests on Solaris Vladimir Marek
2022-04-29 16:09 ` Carlo Marcelo Arenas Belón
2022-04-29 16:48 ` Junio C Hamano [this message]
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=xmqqr15fdedp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Vladimir.Marek@oracle.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
/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).