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: Test failure caused by commit 377028d99
Date: Sat, 21 Sep 2013 09:30:33 +0000	[thread overview]
Message-ID: <20130921093033.GA680@dcvr.yhbt.net> (raw)
In-Reply-To: CAAB-Kc=HhGin-JfKamxPFMhUs1yRnS=uPtmFqyp5weEMMx4BPA@mail.gmail.com

Hleb Valoshka <375gnu@gmail.com> wrote:
> On 9/6/13, Eric Wong <normalperson@yhbt.net> wrote:
> >> > Does the following change increase reliability for you?
> >> Yes, it helps. Thanks.
> > Thanks for testing, pushed as
> > commit ff940137dc5098c9d8094e041e9be053cb3e139f
> 
> Another problem has emerged :) Sometimes ruby delivers signals too
> late and this test dies because of unhandled USR1. At least Ruby2.0 is
> affected (I have no problem with this test under Ruby1.9.3). May be
> it's better to remove it.

Ugh, yes, this is tricky to test...
Does the following help?

diff --git a/test/test_poll.rb b/test/test_poll.rb
index d9a2b07..5c8071d 100644
--- a/test/test_poll.rb
+++ b/test/test_poll.rb
@@ -108,6 +108,8 @@ class TestPoll < Test::Unit::TestCase
     assert_equal({@wr => Kgio::POLLOUT}, res)
     assert diff < 1.0, "diff=#{diff}"
     assert ok
+
+    1000.times { Thread.pass } # let signal handlers fire
     ensure
       trap(:USR1, orig)
   end


(I'm sleepy myself and thinking out loud)
Or it could be just made to sleep (and slow down the tests even more)
Thanks!


  reply	other threads:[~2013-09-21  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 20:14 Test failure caused by commit 377028d99 Hleb Valoshka
2013-09-04 20:51 ` Eric Wong
2013-09-05  7:55   ` Hleb Valoshka
2013-09-05 19:48   ` Hleb Valoshka
2013-09-05 23:13     ` Eric Wong
2013-09-15 19:07       ` Hleb Valoshka
2013-09-21  9:30         ` Eric Wong [this message]
2013-09-24 15:02           ` Hleb Valoshka
2013-09-25 17:46             ` 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/kgio/

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

  git send-email \
    --in-reply-to=20130921093033.GA680@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).