[ 
https://issues.apache.org/jira/browse/NIFI-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302360#comment-15302360
 ] 

ASF GitHub Bot commented on NIFI-1668:
--------------------------------------

Github user JPercivall commented on the pull request:

    https://github.com/apache/nifi/pull/324#issuecomment-221924674
  
    Ah that is an important distinction in regards to the "after" block but 
then how come the that issue wouldn't cause all following tests to fail (since 
FC.shutdown is never executed)?
    
    The first line of the javadoc on ThreadPoolExecutor.execute() says 
"Executes the given task sometime in the future." This means there is no 
guarantee that any of the threads will get executed before "countDownCounter" 
finishes. If it doesn't execute any, and the test fails, it is due to the 
system never scheduling the thread and not due to the thing being tested 
failing.


> Intermittent Test Failure for TestProcessorLifecycle
> ----------------------------------------------------
>
>                 Key: NIFI-1668
>                 URL: https://issues.apache.org/jira/browse/NIFI-1668
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Bryan Bende
>            Assignee: Oleg Zhurakousky
>            Priority: Minor
>             Fix For: 0.7.0
>
>
> A build on Travis produced the errors below, but they are not seen frequently:
> validateProcessorCanBeStoppedWhenOnTriggerThrowsException on 
> validateProcessorCanBeStoppedWhenOnTriggerThrowsException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
>   Time elapsed: 0.085 sec  <<< FAILURE!
> java.nio.channels.OverlappingFileLockException: null
>       at sun.nio.ch.SharedFileLockTable.checkList(FileLockTable.java:255)
>       at sun.nio.ch.SharedFileLockTable.add(FileLockTable.java:152)
>       at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:1043)
>       at java.nio.channels.FileChannel.lock(FileChannel.java:1052)
>       at 
> org.wali.MinimalLockingWriteAheadLog.<init>(MinimalLockingWriteAheadLog.java:179)
>       at 
> org.wali.MinimalLockingWriteAheadLog.<init>(MinimalLockingWriteAheadLog.java:108)
>       at 
> org.apache.nifi.controller.state.providers.local.WriteAheadLocalStateProvider.init(WriteAheadLocalStateProvider.java:97)
>       at 
> org.apache.nifi.controller.state.providers.AbstractStateProvider.initialize(AbstractStateProvider.java:34)
>       at 
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.createStateProvider(StandardStateManagerProvider.java:186)
>       at 
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.createLocalStateProvider(StandardStateManagerProvider.java:80)
>       at 
> org.apache.nifi.controller.state.manager.StandardStateManagerProvider.create(StandardStateManagerProvider.java:66)
>       at 
> org.apache.nifi.controller.FlowController.<init>(FlowController.java:435)
>       at 
> org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:366)
>       at 
> org.apache.nifi.controller.scheduling.TestProcessorLifecycle.buildFlowControllerForTest(TestProcessorLifecycle.java:642)
>       at 
> org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException(TestProcessorLifecycle.java:477)
> Results :
> Failed tests: 
>   
> TestProcessorLifecycle.validateDisableOperation:117->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateLifecycleOperationOrderWithConcurrentCallsToStartStop:254->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessScheduledAfterAdministrativeDelayDueToTheOnScheduledException:347->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnScheduledBlocksIndefinitelyInterruptable:413->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnScheduledBlocksIndefinitelyUninterruptable:443->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnScheduledConstantlyFails:380->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException:477->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateProcessorUnscheduledAndStoppedWhenStopIsCalledBeforeProcessorFullyStarted:311->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateStartSucceedsOnProcessorWithEnabledService:554->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   
> TestProcessorLifecycle.validateStopCallsAreMeaninglessIfProcessorNotStarted:187->buildFlowControllerForTest:642
>  » OverlappingFileLock
>   TestProcessorLifecycle.validateSuccessfullAndOrderlyShutdown:239 
> expected:<3> but was:<2>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to