You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/05/29 13:25:17 UTC

[jira] [Commented] (HADOOP-11979) optionally have test-patch make a partial -1 before long run checks

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

Steve Loughran commented on HADOOP-11979:
-----------------------------------------

this is a nice idea. we could go one further by actually splitting the fast from the slow tests; anything with a minicluster set up tagged as slowr (JUnit 4 categories), and have them skipped on the first round.

> optionally have test-patch make a partial -1 before long run checks
> -------------------------------------------------------------------
>
>                 Key: HADOOP-11979
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11979
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Sean Busbey
>            Priority: Minor
>
> If test-patch has -1s for things that are relatively fast (e.g. javac, checkstyle, whitespace, etc), then it would be nice if it would post a "-1s so far" message to jira before running the long-run phase (i.e. test) similar to what it does now for reexec of dev-support patches.



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