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: Concurrency issue in TestKgioUnixConnect? Date: Thu, 5 Sep 2013 15:35:04 +0300 Message-ID: References: <20130901140301.GI1272@loar> <20130901195835.GB30612@dcvr.yhbt.net> <20130905081408.GA27637@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 1378384518 30391 80.91.229.3 (5 Sep 2013 12:35:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 Sep 2013 12:35:18 +0000 (UTC) To: kgio@librelist.org Original-X-From: kgio@librelist.org Thu Sep 05 14:35:20 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:211 Archived-At: Received: from zedshaw2.xen.prgmr.com ([71.19.156.177]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VHYmM-0003KE-N4 for gclrkg-kgio@m.gmane.org; Thu, 05 Sep 2013 14:35:18 +0200 Received: from zedshaw2.xen.prgmr.com (unknown [IPv6:::1]) by zedshaw2.xen.prgmr.com (Postfix) with ESMTP id C4AB4750A5 for ; Thu, 5 Sep 2013 12:44:20 +0000 (UTC) On 9/5/13, Eric Wong wrote: > "make -j" runs them in parallel, but in completely isolated processes > (not loading unrelated test files, either). I haven't checked, does the > Debian ruby build scripts use threads or load all the tests into the > same process? gem2deb logic is very simple: if exists ruby-tests.rake then run rake ruby-tests.rake else if exists ruby-tests.rb then run ruby ruby-tests.rb else if exists ruby-test-files.yaml then YAML.load('ruby-test-files.yaml').each {|f| require f} end So in 1st and 2nd cases this is the maintainer's job to deside how to run tests but in 3rd everything depends on test/unit from ruby distribution.