unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Ken Dreyer <ktdreyer@ktdreyer.com>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public@bogomips.org, mongrel-unicorn@rubyforge.org
Subject: Re: [PATCH] tests: switch to minitest
Date: Mon, 12 May 2014 18:46:15 -0600	[thread overview]
Message-ID: <CAD3FbMVKBc4xypOXZgZbrzXpoKt92JgAH3ZpRMDbz2jRTZ8Q9A@mail.gmail.com> (raw)
In-Reply-To: <20140426060744.GA17493@dcvr.yhbt.net>

On Sat, Apr 26, 2014 at 12:07 AM, Eric Wong <e@80x24.org> wrote:
> Ken Dreyer <ktdreyer@ktdreyer.com> wrote:
>> Ruby 1.9+ uses Minitest as the backend for Test::Unit. As of Minitest 5,
>> the shim has lost some backwards compatibility. It is time to make the
>> jump to minitest.
>>
>> Adjust the unicorn test suite to support Minitest 5's syntax.
>
> Thank you very much for taking a look at this.  I was going to do it
> myself over the summer.
>
> I ran into some problems with our tests forking + minitest/autorun
> causing some problems due to at_exit usage.

Hi Eric,

Thanks very much for looking over my patch.

I've taken a look at yahns and the changes you made there, and I've
also been testing Unicorn here with my patch. I'm a bit confused about
your comments regarding the problems with forking and
minitest/autorun, because I'm not personally seeing test failures
regarding forking and my patch.

I am seeing one failure with the final assert in
TestSocketHelper#test_bind_listen_unix_rebind, but I don't think
that's a result of this, right?

Would you mind pointing me in the right direction?

- Ken

  reply	other threads:[~2014-05-13  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26  3:20 [PATCH] tests: switch to minitest Ken Dreyer
2014-04-26  6:07 ` Eric Wong
2014-05-13  0:46   ` Ken Dreyer [this message]
2014-05-13  1:13     ` Eric Wong
2014-05-29 19:17       ` Eric Wong

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

  List information: https://yhbt.net/unicorn/

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

  git send-email \
    --in-reply-to=CAD3FbMVKBc4xypOXZgZbrzXpoKt92JgAH3ZpRMDbz2jRTZ8Q9A@mail.gmail.com \
    --to=ktdreyer@ktdreyer.com \
    --cc=e@80x24.org \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=unicorn-public@bogomips.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

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).