[
https://issues.apache.org/jira/browse/NIFI-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602555#comment-14602555
]
Toivo Adams commented on NIFI-727:
----------------------------------
It took 54,195 seconds on my notebook.
And I often wonder why NiFi build takes so much time.
:)
How to solve it?
Just add @Ignore or something else?
It’s stress test which might be sometimes useful, so removing it completely is
also not desirable I think.
Thanks
Toivo
> 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
> 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)
