atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones"<>
Subject Emtity Resource v1 test failures
Date Thu, 24 Aug 2017 14:05:09 GMT
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
java.lang.AssertionError: expected:<??????????> but was:<null>
	at org.apache.atlas.web.integration.EntityJerseyResourceIT.testUTF8(

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

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  <<<
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(

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(

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(

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(
	at org.apache.atlas.web.integration.EntityJerseyResourceIT.testAddReferenceProperty(

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(

Results :

Failed tests: 
  QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API org.apache...
  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


View raw message