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

Andy LoPresto commented on NIFI-5416:
-------------------------------------

The above timings were from a build where my {{/etc/hosts}} file was causing 
some issues and many timeouts were being hit. After resolving that issue, here 
is every test with more than 10 seconds duration:

{code}
$ mvn clean install -Pcontrib-check -Pinclude-grpc 2>&1 | tee 
../maven_test_output.txt
$ grep 'Time elapsed' ../maven_test_output.txt | cut -d ' ' -f 13- | sort -rn > 
../maven_test_timings.txt

95.057 s - in org.apache.nifi.provenance.TestPersistentProvenanceRepository
58.233 s - in org.apache.nifi.processors.standard.TestListFile
42.849 s - in org.apache.nifi.controller.TestFlowController
32.951 s - in org.apache.nifi.processors.standard.TestInvokeHttpTwoWaySSL
32.646 s - in org.apache.nifi.processors.standard.TestInvokeHttpSSL
21.957 s - in org.apache.nifi.controller.scheduling.TestProcessorLifecycle
20.66 s - in org.apache.nifi.controller.repository.TestFileSystemRepository
18.409 s - in org.apache.nifi.processors.standard.TestTailFile
13.03 s - in 
org.apache.nifi.controller.state.providers.zookeeper.TestZooKeeperStateProvider
12.793 s - in org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneTest
12.203 s - in org.apache.nifi.remote.client.http.TestHttpClient
11.106 s - in org.apache.nifi.toolkit.zkmigrator.ZooKeeperMigratorTest
10.719 s - in 
org.apache.nifi.processors.aws.wag.TestInvokeInvokeAmazonGatewayApiWithControllerService
10.419 s - in org.apache.nifi.processors.standard.TestInvokeHTTP
10.318 s - in 
org.apache.nifi.processors.aws.wag.TestInvokeInvokeAmazonGatewayApiWithCredFile
10.278 s - in 
org.apache.nifi.processors.aws.wag.TestInvokeInvokeAmazonGatewayApiWithStaticAuth
{code}

> Move long running tests to special profile or integration tests
> ---------------------------------------------------------------
>
>                 Key: NIFI-5416
>                 URL: https://issues.apache.org/jira/browse/NIFI-5416
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Tools and Build
>    Affects Versions: 1.7.0
>            Reporter: Andy LoPresto
>            Priority: Major
>              Labels: build, integration-test, test
>
> Running the build with tests is a very long process; sometimes a multithread 
> build can be problematic, and running the full build is over half an hour on 
> commodity hardware. 
> Some unit tests wait an inordinate amount of time and do not need to be run 
> as part of the normal build. I've started to identify some of these tests 
> just via repeated runs. Either they should be moved to the integration tests 
> profile, or a new profile / JUnit category to be run only when necessary. 
> A quick collection of significantly longer tests shows the possibility of >6 
> minutes shaved off the build. 
> * TestTailFile 18s
> * TestPostHTTP 35s
> * TestListFile 58s
> * TestListenUDP 39s
> * TestInvokeHttpTwoWaySSL 67s
> * TestInvokeHttpSSL 67s
> * TestInvokeHttp 10s
> * TestGetHTTP 35s
> * TestRELPSocketChannelHandler 36s
> * DBCPServiceTest 37s
> =>400 seconds = 6+ minutes saved



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to