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

Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2015/07/13 22:32:04 UTC

[jira] [Commented] (NIFI-727) TestJdbcHugeStream takes too long

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

Mark Payne commented on NIFI-727:
---------------------------------

I think this is probably more of an integration test. We have a ticket already, NIFI-569. This could probably just be made into a sub-ticket of that one?

> TestJdbcHugeStream takes too long
> ---------------------------------
>
>                 Key: NIFI-727
>                 URL: https://issues.apache.org/jira/browse/NIFI-727
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Joseph Witt
>            Assignee: Toivo Adams
>            Priority: Minor
>             Fix For: 0.3.0
>
>
> Running org.apache.nifi.processors.standard.util.TestJdbcHugeStream
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 45.891 sec - in org.apache.nifi.processors.standard.util.TestJdbcHugeStream
> This has caused the build to be more than 30% longer than previously seen when on high-end machines with many cores.  The length of the test doesn't seem to clearly add value to warrant it so best to make it lean and mean.  Short build times are important.



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