From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS47066 71.19.144.0/20 X-Spam-Status: No, score=-1.2 required=3.0 tests=BAYES_00,FREEMAIL_FROM, FROM_STARTS_WITH_NUMS,MSGID_FROM_MTA_HEADER shortcircuit=no autolearn=no version=3.3.2 Path: news.gmane.org!not-for-mail From: Hleb Valoshka <375gnu@gmail.com> Newsgroups: gmane.comp.lang.ruby.kgio.general Subject: Re: Test failure caused by commit 377028d99 Date: Thu, 5 Sep 2013 10:55:24 +0300 Message-ID: References: <20130904201440.GA14313@deneb> <20130904205114.GA4864@dcvr.yhbt.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1378367735 3630 80.91.229.3 (5 Sep 2013 07:55:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 Sep 2013 07:55:35 +0000 (UTC) To: kgio@librelist.org Original-X-From: kgio@librelist.org Thu Sep 05 09:55:38 2013 Return-path: Envelope-to: gclrkg-kgio@m.gmane.org List-Archive: List-Help: List-Id: List-Post: List-Subscribe: List-Unsubscribe: Precedence: list Original-Sender: kgio@librelist.org Xref: news.gmane.org gmane.comp.lang.ruby.kgio.general:208 Archived-At: Received: from zedshaw2.xen.prgmr.com ([71.19.156.177]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VHUPe-0006jw-15 for gclrkg-kgio@m.gmane.org; Thu, 05 Sep 2013 09:55:34 +0200 Received: from zedshaw2.xen.prgmr.com (unknown [IPv6:::1]) by zedshaw2.xen.prgmr.com (Postfix) with ESMTP id 8411B750AF for ; Thu, 5 Sep 2013 08:04:35 +0000 (UTC) On 9/4/13, Eric Wong wrote: >> On my Debian Sid with kernel 3.11-rc7 4 of 5 invocations of >> test_poll_EINTR_changed finished with failure: > > Thanks for the report. Unfortunately, I can't seem to reproduce it, > here on 1.9.3 nor 2.0.0 with Linux 3.10.10. It also unreproducible on 3.2.46-1+deb7u1 (Debian stable). > The test will probably not work well under heavy load, and I've > considered removing it, even. Current behavior may not be compatible > with all Ruby versions depending on how signal handling is implemented. > > Does the following change increase reliability for you? I'll test it when I return home.