Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/3062
@markap14 at least one relevant to this change test appears brittle and
possible another...
[ERROR] Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
10.413 s <<< FAILURE! - in
org.apache.nifi.controller.queue.clustered.TestSocketLoadBalancedFlowFileQueue
[ERROR]
testChangeInClusterTopologyTriggersRebalanceOnlyOnRemovedNodeIfNecessary(org.apache.nifi.controller.queue.clustered.TestSocketLoadBalancedFlowFileQueue)
Time elapsed: 10.008 s <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 10000
milliseconds
at
org.apache.nifi.controller.queue.clustered.TestSocketLoadBalancedFlowFileQueue.testChangeInClusterTopologyTriggersRebalanceOnlyOnRemovedNodeIfNecessary(TestSocketLoadBalancedFlowFileQueue.java:363)
[ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 2, Time elapsed:
37.795 s <<< FAILURE! - in
org.apache.nifi.controller.scheduling.TestProcessorLifecycle
[ERROR]
validateProcessorCanBeStoppedWhenOnTriggerThrowsException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
Time elapsed: 21.061 s <<< FAILURE!
java.lang.AssertionError
at
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.assertCondition(TestProcessorLifecycle.java:120)
at
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException(TestProcessorLifecycle.java:498)
---
