From: Jonathan Nieder <jrnieder@gmail.com>
To: Mike Blume <blume.mike@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
dborowitz@google.com
Subject: Re: [PATCH v4] Allow TTY tests to run under recent Mac OS
Date: Fri, 14 Nov 2014 15:21:07 -0800 [thread overview]
Message-ID: <20141114232106.GA6527@google.com> (raw)
In-Reply-To: <1415995993-70879-1-git-send-email-blume.mike@gmail.com>
Hi,
Mike Blume wrote:
> TTY tests were previously skipped on all Mac OS systems because of a
> bug where reading from pty master occasionally hung. This bug has since
> been found not to be reproducible under Mac OS 10.9 and 10.10.1.
>
> Therefore, run TTY tests under Mac OS 10.9 (Mavericks) and higher.
*puzzled* Testing on Yosemite with the following script[1]
perl -MIO::Pty -MFile::Copy -e '
for (my $i = 0;; $i++) {
my $master = new IO::Pty;
my $slave = $master->slave;
if (fork == 0) {
close $master or die "close: $!";
open STDOUT, ">&", $slave or die "dup2: $!";
close $slave or die "close: $!";
exec("echo", "hi", $i) or die "exec: $!";
}
close $slave or die "close: $!";
copy($master, \*STDOUT) or die "copy: $!";
close $master or die "close: $!";
wait;
}
'
still seems to hang eventually (after 61 iterations when my officemate
tried it), reproducing the bug.
Do you get a different result?
The bug was originally found in an autobuilder that would run the test
suite when new versions were pushed to check for regressions. Even if
the hang only happened 0.1% of the time, that would get the
autobuilder stuck after a while, which was how the problem got
noticed.
Thanks,
Jonathan
[1] https://rt.cpan.org/Public/Bug/Display.html?id=65692
next prev parent reply other threads:[~2014-11-14 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 20:13 [PATCH v4] Allow TTY tests to run under recent Mac OS Mike Blume
2014-11-14 20:20 ` Junio C Hamano
2014-11-14 23:21 ` Jonathan Nieder [this message]
2014-11-14 23:29 ` Junio C Hamano
2014-11-15 0:14 ` John Szakmeister
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=20141114232106.GA6527@google.com \
--to=jrnieder@gmail.com \
--cc=blume.mike@gmail.com \
--cc=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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