You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/12/10 18:54:11 UTC

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

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

Joseph Witt updated NIFI-727:
-----------------------------
    Fix Version/s:     (was: 0.5.0)
                   0.4.0

> 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: Joseph Witt
>            Priority: Minor
>             Fix For: 0.4.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)