[
https://issues.apache.org/jira/browse/TINKERPOP3-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Plurad updated TINKERPOP3-906:
------------------------------------
Description:
Original issue: The {{DependencyGrabberTest}} currently require ordered
execution based on the name of the test. In some environments this seems to
cause the tests to fail (as they may execute out of order). Generally speaking
though it seems it would be best if the tests didn't have dependencies on each
other in order to pass.
Actual issue: It turns out that there is a bug in Groovy Grapes. When there is
a failed call to {{Grape.resolve()}}, {{GrapeIvy.resolve()}} hangs onto a
reference to the IvyGrabRecord for the failed dependency. When subsequent
{{resolve()}} calls are made, those failed records are still there, so it will
continue to fail from that point on. This explains why the ordering was
important in the TinkerPop test case.
{noformat}
\,,,/
(o o)
-----oOOo-(3)-oOOo-----
plugin activated: tinkerpop.server
plugin activated: tinkerpop.utilities
plugin activated: tinkerpop.tinkergraph
gremlin> :install bogus bogus 1.0
==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not found]
gremlin> :install org.apache.tinkerpop hadoop-gremlin 3.0.1-incubating
==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not found]
{noformat}
was:
Original issue: The {{DependencyGrabberTest}} currently require ordered
execution based on the name of the test. In some environments this seems to
cause the tests to fail (as they may execute out of order). Generally speaking
though it seems it would be best if the tests didn't have dependencies on each
other in order to pass.
Actual issue:
{noformat}
\,,,/
(o o)
-----oOOo-(3)-oOOo-----
plugin activated: tinkerpop.server
plugin activated: tinkerpop.utilities
plugin activated: tinkerpop.tinkergraph
gremlin> :install bogus bogus 1.0
==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not found]
gremlin> :install org.apache.tinkerpop hadoop-gremlin 3.0.1-incubating
==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not found]
{noformat}
> Install plugin always fails after first unresolved dependency
> -------------------------------------------------------------
>
> Key: TINKERPOP3-906
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-906
> Project: TinkerPop 3
> Issue Type: Bug
> Components: groovy
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: Jason Plurad
>
> Original issue: The {{DependencyGrabberTest}} currently require ordered
> execution based on the name of the test. In some environments this seems to
> cause the tests to fail (as they may execute out of order). Generally
> speaking though it seems it would be best if the tests didn't have
> dependencies on each other in order to pass.
> Actual issue: It turns out that there is a bug in Groovy Grapes. When there
> is a failed call to {{Grape.resolve()}}, {{GrapeIvy.resolve()}} hangs onto a
> reference to the IvyGrabRecord for the failed dependency. When subsequent
> {{resolve()}} calls are made, those failed records are still there, so it
> will continue to fail from that point on. This explains why the ordering was
> important in the TinkerPop test case.
> {noformat}
> \,,,/
> (o o)
> -----oOOo-(3)-oOOo-----
> plugin activated: tinkerpop.server
> plugin activated: tinkerpop.utilities
> plugin activated: tinkerpop.tinkergraph
> gremlin> :install bogus bogus 1.0
> ==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not
> found]
> gremlin> :install org.apache.tinkerpop hadoop-gremlin 3.0.1-incubating
> ==>Error grabbing Grapes -- [unresolved dependency: bogus#bogus;1.0: not
> found]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
