Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 1 Dec 2011 14:00:41 +0000 (UTC)
From: "nkeywal (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1889170995.31005.1322748041171.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <760323942.2365.1321967080307.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-4847) Activate single jvm for small tests
 on jenkins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nkeywal updated HBASE-4847:
---------------------------

    Status: Patch Available  (was: Open)
    
> Activate single jvm for small tests on jenkins
> ----------------------------------------------
>
>                 Key: HBASE-4847
>                 URL: https://issues.apache.org/jira/browse/HBASE-4847
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, test
>    Affects Versions: 0.94.0
>         Environment: build
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>         Attachments: 4847_all.v4.patch, 4847_all.v5.patch, 4847_all.v6.patch, 4847_all.v6.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_all.v7.patch, 4847_pom.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v2.patch, 4847_pom.v3.patch
>
>
> This will not revolutionate performances alone. We will win between 1 to 4 minutes.
> But we win as well:
>  - it's a step for parallelizing the tests
>  - new tests are less expensive as they do not create a new jvm: it's a continuous win
>  - it will allow to push it on dev env while having the same env on dev & on build, and 3 minutes are 10% of small + medium tests execution time.
> I will do a few "submit patch" to see if it works well before asking for the real commit.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira