From: Jeff King <peff@peff.net>
To: Michael Blume <blume.mike@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: TTY tests are unnecessarily suppressed under Mac OS
Date: Thu, 13 Nov 2014 15:20:00 -0500 [thread overview]
Message-ID: <20141113201959.GD3869@peff.net> (raw)
In-Reply-To: <CAO2U3QhB6rSfJn5ODE8-n2XWuBw8BePqDpQbNdx6LyWy=OFbcg@mail.gmail.com>
On Wed, Nov 12, 2014 at 02:25:52PM -0800, Michael Blume wrote:
> From lib_terminal.sh:
>
> # Reading from the pty master seems to get stuck _sometimes_
> # on Mac OS X 10.5.0, using Perl 5.10.0 or 5.8.9.
> #
> # Reproduction recipe: run
> #
> # i=0
> # while ./test-terminal.perl echo hi $i
> # do
> # : $((i = $i + 1))
> # done
> #
> # After 2000 iterations or so it hangs.
> # https://rt.cpan.org/Ticket/Display.html?id=65692
> #
> test "$(uname -s)" != Darwin &&
>
> I tried the reproduction recipe on my mac and couldn't reproduce, so
> it may make sense to take this switch out? In any case, I've set my
> automated mac build to include TTY tests
10.5.0 is pretty ancient at this point; I can well believe that the
upstream problem has been fixed. It would be nice if we knew in which
version it was fixed, though. Just dropping the restriction risks people
getting spurious failures if they are on an old enough version.
Do you want to roll a patch that checks $(uname) to see if we're on a
recent-enough version (where we can just be conservative, and assume
whatever version you have is the first one to fix it)?
-Peff
next prev parent reply other threads:[~2014-11-13 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 22:25 TTY tests are unnecessarily suppressed under Mac OS Michael Blume
2014-11-13 20:20 ` Jeff King [this message]
[not found] ` <CAO2U3QjGKYLRNWOWeoxqc_kmsdvhB5yfeRwQPuxTtf8n0XjBGA@mail.gmail.com>
2014-11-13 21:10 ` Jeff King
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=20141113201959.GD3869@peff.net \
--to=peff@peff.net \
--cc=blume.mike@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).