[
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481169#comment-16481169
]
ASF GitHub Bot commented on NIFI-5186:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/2722
@mcgilman @markap14 this test finding is related to Mark's preceding PR for
this most likely but
`[ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 2, Time elapsed:
16.555 s <<< FAILURE! - in
org.apache.nifi.controller.scheduling.TestProcessorLifecycle
[ERROR]
validateProcessorCanBeStoppedWhenOnTriggerThrowsException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
Time elapsed: 3.11 s <<< FAILURE!
java.lang.AssertionError
at
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.assertCondition(TestProcessorLifecycle.java:116)
at
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException(TestProcessorLifecycle.java:496)
`
Otherwise, I'm doing some functional testing now and obviously
contrib-check is good. This is really cool and will greatly aid flow
performance for large scale flows or user code in validation that doesn't
behave nicely.
> Update UI to account for asynchronous validation
> ------------------------------------------------
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation
> introduces a new state VALIDATING. This VALIDATING state will be entered
> following any modifications (create, update) to the component (Processor,
> Controller Service, Reporting Task). All component validation is done in the
> background on a recurring interval. When obtaining the current state, we will
> return the last known state unless it is VALIDATING as a result of a
> modification.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
