atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sarath Subramanian <sar...@apache.org>
Subject Re: Emtity Resource v1 test failures
Date Thu, 24 Aug 2017 17:45:42 GMT
Hi Nigel,

Few Integration Test fixes have gone into master in the last couple of
days, could you rebase master and try the tests again.


Thanks,
Sarath Subramanian

On Thu, Aug 24, 2017 at 7:05 AM, Nigel Jones <nigel.l.jones@gmail.com>
wrote:

> Whilst working with ATLAS-2012 (effectively being build under Ubuntu
> 16-10) I hit a unit test error with the v1 api at:
>
>
>
> Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 176.24
> sec <<< FAILURE! - in TestSuite
> testUTF8(org.apache.atlas.web.integration.EntityJerseyResourceIT)  Time
> elapsed: 0.202 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<??????????> but was:<null>
>         at org.apache.atlas.web.integration.EntityJerseyResourceIT.
> testUTF8(EntityJerseyResourceIT.java:840)
>
>
> Results :
>
> Failed tests:
>   EntityJerseyResourceIT.testUTF8:840 expected:<??????????> but was:<null>
>
>
>
> whilst in a standalone environment (Mac) the same tests gave me issues,
> but this time seemingly timeouts
>
>
>
> Tests run: 133, Failures: 5, Errors: 0, Skipped: 5, Time elapsed: 306.586
> sec <<< FAILURE! - in TestSuite
> runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed:
> 0.341 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@e3c98f5 failed with status 409
> (Conflict) Response Body ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given
> type Dimension already exists"})
>         at org.apache.atlas.examples.QuickStartV2IT.runQuickStart(
> QuickStartV2IT.java:49)
>
> testDeleteByQualifiedName(org.apache.atlas.notification.NotificationHookConsumerIT)
> Time elapsed: 60.127 sec  <<< FAILURE!
> java.lang.Exception: Waiting timed out after 60000 msec
>         at org.apache.atlas.notification.NotificationHookConsumerIT.
> testDeleteByQualifiedName(NotificationHookConsumerIT.java:184)
>
> testUpdateEntityPartial(org.apache.atlas.notification.NotificationHookConsumerIT)
> Time elapsed: 60.033 sec  <<< FAILURE!
> java.lang.Exception: Waiting timed out after 60000 msec
>         at org.apache.atlas.notification.NotificationHookConsumerIT.
> testUpdateEntityPartial(NotificationHookConsumerIT.java:127)
>
> testAddReferenceProperty(org.apache.atlas.web.integration.EntityJerseyResourceIT)
> Time elapsed: 0.08 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<2>
>         at org.apache.atlas.web.integration.EntityJerseyResourceIT.
> addProperty(EntityJerseyResourceIT.java:476)
>         at org.apache.atlas.web.integration.EntityJerseyResourceIT.
> testAddReferenceProperty(EntityJerseyResourceIT.java:451)
>
> testPartialUpdate(org.apache.atlas.web.integration.EntityJerseyResourceIT)
> Time elapsed: 0.061 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<3>
>         at org.apache.atlas.web.integration.EntityJerseyResourceIT.
> testPartialUpdate(EntityJerseyResourceIT.java:878)
>
>
> Results :
>
> Failed tests:
>   QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API
> org.apache...
>   NotificationHookConsumerIT.testDeleteByQualifiedName:184->BaseResourceIT.waitFor:626
> »
>   NotificationHookConsumerIT.testUpdateEntityPartial:127->BaseResourceIT.waitFor:626
> »
>   EntityJerseyResourceIT.testAddReferenceProperty:451->addProperty:476
> expected:<1> but was:<2>
>   EntityJerseyResourceIT.testPartialUpdate:878 expected:<1> but was:<3>
>
> Tests run: 133, Failures: 5, Errors: 0, Skipped: 5
>
>
>
> I can raise JIRA, but I have a feeling this module was problematic before.
> Is anyone looking at these currently? I also may be a few days behind
> master, but not much
>
> Thanks
> Nigel.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message