[
https://issues.apache.org/jira/browse/NIFI-11737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735914#comment-17735914
]
ASF subversion and git services commented on NIFI-11737:
--------------------------------------------------------
Commit 9709bd6fb749e1a1c7bc52076e69d96f5235802a in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9709bd6fb7 ]
NIFI-11737: Improved performance of FlowSynchronizationIT
- FlowSynchronizationIT no longer requires isDestroyEnvironmentAfterEachTest to
return true
This closes #7420
Signed-off-by: David Handermann <[email protected]>
> Refactor FlowSynchronizationIT to avoid restarting the nifi instances between
> each test
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-11737
> URL: https://issues.apache.org/jira/browse/NIFI-11737
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
>
> When the FlowSynchronizationIT was created it had a handful of tests. TO
> ensure that each of them was starting with a clean slate, we override
> {{isDestroyEnvironmentAfterEachTest}} to return {{{}true{}}}. However, more
> tests have been added to this class over time. As a result, the amount of
> time that the class takes to run has gotten longer and longer. At this point
> it typically takes over 20 minutes in Github Actions to complete just this
> one test class.
> This is because each of these tests has to start a two-node cluster, wait for
> both nodes to start, perform the test, and shutdown the nodes. With some
> slight refactoring of the tests, though, we should be able to avoid shutting
> down and tearing down the cluster for each test. This should significantly
> improve the amount of time needed for the tests to run.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
