Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 2 Jul 2015 19:19:04 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12842173.1435804277000.88313.1435864744659@Atlassian.JIRA>
In-Reply-To: <JIRA.12842173.1435804277000@Atlassian.JIRA>
References: <JIRA.12842173.1435804277000@Atlassian.JIRA>
 <JIRA.12842173.1435804277158@arcas>
Subject: [jira] [Commented] (ACCUMULO-3929) Separate
 performance/timing-sensitive tests from the rest of integration tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612400#comment-14612400 ] 

Eric Newton commented on ACCUMULO-3929:
---------------------------------------

I've attached a patch that disables performance-sensitive tests if they are being run under map-reduce. I'm not sure if it's the right way to go, or if we just make the mapper detect a properly annotated test.

> Separate performance/timing-sensitive tests from the rest of integration tests
> ------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3929
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3929
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>
>         Attachments: ACCUMULO-3929-01.patch
>
>
> Sometimes in the course of fixing bugs in Accumulo, we want to write tests that are sensitive to certain performance characteristics of the underlying hardware.
> These kinds of tests are important in helping us catch regressions, but they're not suitable to run as a normal part of the integration test suite.
> We can separate these tests by creating a special Java annotation and the Category support on the [surefire plugin|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_JUnit_Categories].
> The difficulty will likely be in how we want to run these tests. It should be very straightfoward to _only_ run the performance tests. Maybe more work if we want to be able to run all the normal ITs and these performance tests. Not entirely sure. HBase's top-level pom has some examples of setting up multiple executions of the surefire-plugin.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)