[ 
https://issues.apache.org/jira/browse/ATLAS-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nigel Jones closed ATLAS-2234.
------------------------------

> Unit test failures in NotificationHookConsumerTest.java
> -------------------------------------------------------
>
>                 Key: ATLAS-2234
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2234
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Nigel Jones
>            Priority: Major
>
> Have been seeing this unit test failure for a while on my local MacOS builds 
> off master.
> Running org.apache.atlas.notification.NotificationHookConsumerTest
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.46 sec <<< 
> FAILURE! - in org.apache.atlas.notification.NotificationHookConsumerTest
> consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(org.apache.atlas.notification.NotificationHookConsumerTest)
>   Time elapsed: 2.52 sec  <<< FAILURE!
> java.lang.AssertionError: expected [false] but found [true]
>       at org.testng.Assert.fail(Assert.java:94)
>       at org.testng.Assert.failNotEquals(Assert.java:496)
>       at org.testng.Assert.assertFalse(Assert.java:63)
>       at org.testng.Assert.assertFalse(Assert.java:73)
>       at 
> org.apache.atlas.notification.NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(NotificationHookConsumerTest.java:290)
> ....
> Results :
> Failed tests: 
>   
> NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted:290
>  expected [false] but found [true]
> Tests run: 79, Failures: 1, Errors: 0, Skipped: 0
> ....
> [INFO] Apache Atlas UI .................................... SUCCESS [ 57.722 
> s]
> [INFO] Apache Atlas Web Application ....................... FAILURE [ 51.658 
> s]
> [INFO] Apache Atlas Documentation ......................... SKIPPED
> this came up again whilst verifying another fix. Opening, will return after 
> completing the other changes.
> It appears this is likely a timing issue probably due to 2500ms vs 500ms.. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to