kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Jeremy Evans <>
Subject: Re: Current test failures on OpenBSD
Date: Tue, 15 Nov 2011 17:56:23 -0800	[thread overview]
Message-ID: <20111116015623.GJ17621@jeremyevans.local> (raw)

On 11/15 01:35, Eric Wong wrote:
> Eric Wong <> wrote:
> > I'll fix the tests and documentation in a few.
> I've pushed out the following changes to
> master on git://
> (commit 48dc3c5a1943801311567e72a8e69fcb0cd8cf8d)
> Eric Wong (3):
>       accept: always set O_NONBLOCK for accept()-ed sockets in 1.8
>       accept: deprecate singleton Kgio.accept_* methods
>       tests: remove tests for IO#nonblock? after accept
> Can you please test?  Thanks!


Passes all tests on OpenBSD.


      reply	other threads:[~2011-11-16  1:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  0:42 Current test failures on OpenBSD Jeremy Evans
2011-11-15  3:26 ` Eric Wong
2011-11-15 15:52   ` Jeremy Evans
2011-11-15 21:01     ` Eric Wong
2011-11-15 21:35       ` Eric Wong
2011-11-16  1:56         ` Jeremy Evans [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111116015623.GJ17621@jeremyevans.local \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).