You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by Nigel Jones <ni...@gmail.com> on 2017/08/24 14:05:09 UTC
Emtity Resource v1 test failures
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.
Re: Emtity Resource v1 test failures
Posted by Nigel Jones <ni...@gmail.com>.
I opened up ATLAS-2096 on the Dimension already exists error which I continue to hit today after pulling the latest master, and I also see intermittently in the Jenkins build.
On 2017-08-25 19:10, Sarath Subramanian <sa...@apache.org> wrote:
> Nigel,
> I agree we all need to spend some time and clean up these tests. Feel free
> to open JIRA's for the failing tests.
>
> I see the integration tests consistently failing in hive-bridge module due
> to Lock timeout exception - I suspect this is because of some stale open
> transaction lingering around which also modified/read the same property,
> since Berkley DB is ACID compliant subsequent transactions times out since
> the previous transaction is not closed properly. We don't see this in HBase
> since its not an ACID compliant.
>
>
> Thanks,
> Sarath Subramanian
>
> On Fri, Aug 25, 2017 at 7:10 AM, Apoorv Naik <an...@hortonworks.com> wrote:
>
> > I think Sarath already made changes for this one don't know why this
> > failed again. Perhaps we need to revisit the integration tests after all.
> >
> > One jira per test failure should be a great way to split work amongst the
> > community.
> >
> > Sent from Nine<http://www.9folders.com/>
> > ________________________________
> > From: Nigel Jones <ni...@gmail.com>
> > Sent: Aug 25, 2017 5:06 AM
> > To: dev@atlas.apache.org
> > Subject: Re: Emtity Resource v1 test failures
> >
> >
> > On 2017-08-25 12:28, "Nigel Jones"<ni...@gmail.com> wrote:
> >
> > > I rebased this morning, but am still getting a failure - albeit a
> > different one - this looks like a timeout issue whilst the previous were
> > seemingly more functional. Is there a JIRA you are tracking these under?
> > Should I create one per failure?
> > >
> > > I'll retry
> > >
> > > Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> > 109.969 sec <<< FAILURE! - in TestSuite
> > > testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT) Time
> > elapsed: 1.537 sec <<< FAILURE!
> >
> > Another build, another random error - timing could be a factor (certainly
> > in the earlier test). This however is one of the build failures I had
> > yesterday. It's also been seen in the Jenkins build
> >
> > FAILURE! - in TestSuite
> > runQuickStart(org.apache.atlas.examples.QuickStartV2IT) Time elapsed:
> > 0.344 sec <<< FAILURE!
> > org.apache.atlas.AtlasServiceException: Metadata service API
> > org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 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)
> >
> >
> > Results :
> >
> > Failed tests:
> > QuickStartV2IT.runQuickStart:49 û AtlasService Metadata service API
> > org.apache...
> >
> > Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
> >
> >
> > I feel we do need to between us all try and get these tests running
> > cleanly, as it's otherwise very tempting to run skip-tests and risk
> > suggesting a change/patch that causes a failure. (I was trying to get a
> > solid baseline before trying to start on a new API)
> >
> > We could even consider a short term change to the build to not stop if any
> > known, problematic tests fail - still run, but continue. may help?
> >
> >
>
Re: Emtity Resource v1 test failures
Posted by Sarath Subramanian <sa...@apache.org>.
Nigel,
I agree we all need to spend some time and clean up these tests. Feel free
to open JIRA's for the failing tests.
I see the integration tests consistently failing in hive-bridge module due
to Lock timeout exception - I suspect this is because of some stale open
transaction lingering around which also modified/read the same property,
since Berkley DB is ACID compliant subsequent transactions times out since
the previous transaction is not closed properly. We don't see this in HBase
since its not an ACID compliant.
Thanks,
Sarath Subramanian
On Fri, Aug 25, 2017 at 7:10 AM, Apoorv Naik <an...@hortonworks.com> wrote:
> I think Sarath already made changes for this one don't know why this
> failed again. Perhaps we need to revisit the integration tests after all.
>
> One jira per test failure should be a great way to split work amongst the
> community.
>
> Sent from Nine<http://www.9folders.com/>
> ________________________________
> From: Nigel Jones <ni...@gmail.com>
> Sent: Aug 25, 2017 5:06 AM
> To: dev@atlas.apache.org
> Subject: Re: Emtity Resource v1 test failures
>
>
> On 2017-08-25 12:28, "Nigel Jones"<ni...@gmail.com> wrote:
>
> > I rebased this morning, but am still getting a failure - albeit a
> different one - this looks like a timeout issue whilst the previous were
> seemingly more functional. Is there a JIRA you are tracking these under?
> Should I create one per failure?
> >
> > I'll retry
> >
> > Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 109.969 sec <<< FAILURE! - in TestSuite
> > testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT) Time
> elapsed: 1.537 sec <<< FAILURE!
>
> Another build, another random error - timing could be a factor (certainly
> in the earlier test). This however is one of the build failures I had
> yesterday. It's also been seen in the Jenkins build
>
> FAILURE! - in TestSuite
> runQuickStart(org.apache.atlas.examples.QuickStartV2IT) Time elapsed:
> 0.344 sec <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 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)
>
>
> Results :
>
> Failed tests:
> QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API
> org.apache...
>
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
>
>
> I feel we do need to between us all try and get these tests running
> cleanly, as it's otherwise very tempting to run skip-tests and risk
> suggesting a change/patch that causes a failure. (I was trying to get a
> solid baseline before trying to start on a new API)
>
> We could even consider a short term change to the build to not stop if any
> known, problematic tests fail - still run, but continue. may help?
>
>
Re: Emtity Resource v1 test failures
Posted by Apoorv Naik <an...@hortonworks.com>.
I think Sarath already made changes for this one don't know why this failed again. Perhaps we need to revisit the integration tests after all.
One jira per test failure should be a great way to split work amongst the community.
Sent from Nine<http://www.9folders.com/>
________________________________
From: Nigel Jones <ni...@gmail.com>
Sent: Aug 25, 2017 5:06 AM
To: dev@atlas.apache.org
Subject: Re: Emtity Resource v1 test failures
On 2017-08-25 12:28, "Nigel Jones"<ni...@gmail.com> wrote:
> I rebased this morning, but am still getting a failure - albeit a different one - this looks like a timeout issue whilst the previous were seemingly more functional. Is there a JIRA you are tracking these under? Should I create one per failure?
>
> I'll retry
>
> Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec <<< FAILURE! - in TestSuite
> testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT) Time elapsed: 1.537 sec <<< FAILURE!
Another build, another random error - timing could be a factor (certainly in the earlier test). This however is one of the build failures I had yesterday. It's also been seen in the Jenkins build
FAILURE! - in TestSuite
runQuickStart(org.apache.atlas.examples.QuickStartV2IT) Time elapsed: 0.344 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 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)
Results :
Failed tests:
QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API org.apache...
Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
I feel we do need to between us all try and get these tests running cleanly, as it's otherwise very tempting to run skip-tests and risk suggesting a change/patch that causes a failure. (I was trying to get a solid baseline before trying to start on a new API)
We could even consider a short term change to the build to not stop if any known, problematic tests fail - still run, but continue. may help?
Re: Emtity Resource v1 test failures
Posted by Nigel Jones <ni...@gmail.com>.
On 2017-08-25 12:28, "Nigel Jones"<ni...@gmail.com> wrote:
> I rebased this morning, but am still getting a failure - albeit a different one - this looks like a timeout issue whilst the previous were seemingly more functional. Is there a JIRA you are tracking these under? Should I create one per failure?
>
> I'll retry
>
> Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec <<< FAILURE! - in TestSuite
> testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT) Time elapsed: 1.537 sec <<< FAILURE!
Another build, another random error - timing could be a factor (certainly in the earlier test). This however is one of the build failures I had yesterday. It's also been seen in the Jenkins build
FAILURE! - in TestSuite
runQuickStart(org.apache.atlas.examples.QuickStartV2IT) Time elapsed: 0.344 sec <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 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)
Results :
Failed tests:
QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API org.apache...
Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
I feel we do need to between us all try and get these tests running cleanly, as it's otherwise very tempting to run skip-tests and risk suggesting a change/patch that causes a failure. (I was trying to get a solid baseline before trying to start on a new API)
We could even consider a short term change to the build to not stop if any known, problematic tests fail - still run, but continue. may help?
Re: Emtity Resource v1 test failures
Posted by Nigel Jones <ni...@gmail.com>.
On 2017-08-24 18:45, Sarath Subramanian <sa...@apache.org> wrote:
> 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.
Hi Sarath,
I rebased this morning, but am still getting a failure - albeit a different one - this looks like a timeout issue whilst the previous were seemingly more functional. Is there a JIRA you are tracking these under? Should I create one per failure?
I'll retry
Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec <<< FAILURE! - in TestSuite
testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT) Time elapsed: 1.537 sec <<< FAILURE!
java.lang.AssertionError:
at org.apache.atlas.examples.QuickStartIT.testLineageIsMaintained(QuickStartIT.java:130)
Results :
Failed tests:
QuickStartIT.testLineageIsMaintained:130
Re: Emtity Resource v1 test failures
Posted by Sarath Subramanian <sa...@apache.org>.
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 <ni...@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.
>