kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: kgio@librelist.org
Subject: Re: kgio test_signal_close failed
Date: Wed, 7 Mar 2012 10:16:12 +0000	[thread overview]
Message-ID: <20120307101612.GA31001@dcvr.yhbt.net> (raw)
In-Reply-To: CALiegf=tah9dzOd4D=unBkesQ1Zy12i=hb7KbcBf_FM5fnG5sg@mail.gmail.com

Iñaki Baz Castillo <ibc@aliax.net> wrote:
> Hi Eric, how to test the test files? "rake test" does nothing.

GNU make.  I just pushed the following out:

Thanks for testing :>

From 2c2befb1caa47fe3bf2e6d31dd0733956d178c87 Mon Sep 17 00:00:00 2001
From: Eric Wong <normalperson@yhbt.net>
Date: Wed, 7 Mar 2012 10:14:17 +0000
Subject: [PATCH] HACKING: add instructions for running tests

Unlike most Rubyists, I prefer GNU make to Rake.
---
 HACKING |   15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/HACKING b/HACKING
index 004bcbb..5d485be 100644
--- a/HACKING
+++ b/HACKING
@@ -61,3 +61,18 @@ Without RubyGems (via setup.rb):
 
 It is not at all recommended to mix a RubyGems installation with an
 installation done without RubyGems, however.
+
+=== Tests
+
+We use GNU make to run tests in parallel.  test/unit/parallel didn't
+exist for old versions of Ruby before 1.9.3.  Users of GNU-based systems
+(such as GNU/Linux) usually have GNU make installed as "make" instead of
+"gmake".
+
+Running the entire test suite with 4 tests in parallel:
+
+  gmake -j4 test
+
+Running just one unit test:
+
+  gmake test/test_poll.rb

  reply	other threads:[~2012-03-07 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 16:12 kgio test_signal_close failed 375gnu
2012-03-04 19:17 ` Eric Wong
2012-03-05 18:56   ` 375gnu
2012-03-05 22:30     ` Eric Wong
2012-03-06 16:34       ` 375gnu
2012-03-07  9:17         ` Eric Wong
2012-03-07  9:51           ` Iñaki Baz Castillo
2012-03-07 10:16             ` Eric Wong [this message]
2012-03-07 10:23               ` Iñaki Baz Castillo

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/kgio/

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

  git send-email \
    --in-reply-to=20120307101612.GA31001@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=kgio@librelist.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/kgio.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).