Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9BC09C80 for ; Wed, 2 May 2012 10:54:14 +0000 (UTC) Received: (qmail 17162 invoked by uid 500); 2 May 2012 10:54:13 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 17105 invoked by uid 500); 2 May 2012 10:54:13 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 17098 invoked by uid 99); 2 May 2012 10:54:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 10:54:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of serera@gmail.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2012 10:54:06 +0000 Received: by obbef5 with SMTP id ef5so1048652obb.35 for ; Wed, 02 May 2012 03:53:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pWigyYe5hQbyVt4QyHHFP0WwtsjdbiTgAKm8TfnlbK0=; b=KL/MubCL84fhhiTx5x/5URqGLTkejvjGn9LBE8HRqmnhcEMDOxEX9gX89YfggGytSn QA9f/toqfU2gred6M8yrcdnTQ2SeVOKJBi5N+Z/fSUBwGRLYVsB11MFZwuZHHfHdw1lD UB8G3NLY6/meDccoXPzZZf0ww5oLgNQib1Dg5f5sOvlBzY7HWX4GDXL7WNCJr8JNztQY 2dMOIiGHGbJLmvMh3jKU2zTTGRPS4PDvuCgvWlYt5pB+K1F32dxpeCIoaN4h4NKNLns5 hujuBi6l4KkdM4jTkZneSCizD0sfSY2zkpADyq8AoUyLqb7kU3Q0Pc8cDOMS7WXS5P2j +KwQ== MIME-Version: 1.0 Received: by 10.60.14.226 with SMTP id s2mr8515892oec.29.1335956025768; Wed, 02 May 2012 03:53:45 -0700 (PDT) Received: by 10.182.19.168 with HTTP; Wed, 2 May 2012 03:53:45 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 May 2012 13:53:45 +0300 Message-ID: Subject: Re: hudson hung From: Shai Erera To: dev@lucene.apache.org Content-Type: multipart/alternative; boundary=e89a8fb1f9c459f99304bf0b8012 --e89a8fb1f9c459f99304bf0b8012 Content-Type: text/plain; charset=ISO-8859-1 Yes I figured it has to do with the runner. Good though that I can control it with a -Dtests.timeout property. I guess that I need to specify that as sysproperty in my build.xml? Shai On Wed, May 2, 2012 at 1:39 PM, Dawid Weiss wrote: > > Can I use the randomized.jar with Lucene 3.6 test-framework? I guess not > > Yes and no. You'd need to integrate the sources (LuceneTestCase) with > the runner first (@RunWith(RandomizedRunner.class)). I haven't tested > 3.6 but there are nuances that go beyond trivial substitutions. See > the patch when this was done for the trunk and you'll see how large > the commit was. > > > because the Timeout annotation doesn't work - I added it with millis=10 > but > > a test ran for 20 seconds uninterrupted. > > It's because this annotation is supported only by the runner above. > The default JUnit runner doesn't know anything about it so it's > ignored. > > > Also, what I did with JUnit's timeout is control the timeout through a > > system property -- how do I do that with the randomized timeout? > > Yes, you can control the timeouts globally via > -Dtests.timeout=[millis] (or an annotation on the superclass). Again, > this requires that a suite is executed under randomized runner (not > the default one from junit). > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org > For additional commands, e-mail: dev-help@lucene.apache.org > > --e89a8fb1f9c459f99304bf0b8012 Content-Type: text/html; charset=ISO-8859-1
Yes I figured it has to do with the runner. Good though that I can control it with a -Dtests.timeout property.

I guess that I need to specify that as sysproperty in my build.xml?

Shai

On Wed, May 2, 2012 at 1:39 PM, Dawid Weiss <dawid.weiss@cs.put.poznan.pl> wrote:
> Can I use the randomized.jar with Lucene 3.6 test-framework? I guess not

Yes and no. You'd need to integrate the sources (LuceneTestCase) with
the runner first (@RunWith(RandomizedRunner.class)). I haven't tested
3.6 but there are nuances that go beyond trivial substitutions. See
the patch when this was done for the trunk and you'll see how large
the commit was.

> because the Timeout annotation doesn't work - I added it with millis=10 but
> a test ran for 20 seconds uninterrupted.

It's because this annotation is supported only by the runner above.
The default JUnit runner doesn't know anything about it so it's
ignored.

> Also, what I did with JUnit's timeout is control the timeout through a
> system property -- how do I do that with the randomized timeout?

Yes, you can control the timeouts globally via
-Dtests.timeout=[millis] (or an annotation on the superclass). Again,
this requires that a suite is executed under randomized runner (not
the default one from junit).

Dawid

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


--e89a8fb1f9c459f99304bf0b8012--