You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by joewitt <gi...@git.apache.org> on 2018/05/18 20:37:28 UTC

[GitHub] nifi issue #2722: NIFI-5186: Updating UI to support asynchronous validation

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.


---