[
https://issues.apache.org/jira/browse/NIFI-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688574#comment-16688574
]
ASF subversion and git services commented on NIFI-5824:
-------------------------------------------------------
Commit be0949570a66f672e128ac97c936df546c7d2521 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=be09495 ]
NIFI-5824: Added unit test to FlowController to ensure that the
ProcessScheduler that it creates is properly initialized. Also updated the
properties file used by TestFlowController to use a VolatileContentRepository
instead of FileSystemRepository, and fixed EventDrivenWorkerQueue to return if
calls to poll() are interrupted (via Thread.interrupt) - making these minor
fixes resulted in the unit test TestFlowController running in 2 seconds instead
of 30+ seconds on my machine
This closes #3173.
Signed-off-by: Bryan Bende <[email protected]>
> Add test to FlowController to ensure that NIFI-5822 is properly resolved
> ------------------------------------------------------------------------
>
> Key: NIFI-5824
> URL: https://issues.apache.org/jira/browse/NIFI-5824
> Project: Apache NiFi
> Issue Type: Test
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.9.0
>
>
> While the fix for NIFI-5822 has been merged and addresses the issue, it would
> be helpful to have a unit test to verify it, so that we can ensure that we
> never get into this situation again. It's a slight change that could easily
> be undone in the future and it's not obvious until specific processors
> attempt to run. We should have a unit test to verify that the Process
> Scheduler is able to properly access the ControllerServiceProvider
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
