Stephen Mallette created TINKERPOP-2552:
-------------------------------------------
Summary: Intermittent failure of .NET with pageRank()
Key: TINKERPOP-2552
URL: https://issues.apache.org/jira/browse/TINKERPOP-2552
Project: TinkerPop
Issue Type: Bug
Components: dotnet
Affects Versions: 3.4.10
Reporter: Stephen Mallette
I've been ignoring this failure in Travis for a while now, but every so often
we get a failure in .NET with:
{code}
1) g_V_pageRank_hasXpageRankX: Failed
Gremlin.Net.Driver.Exceptions.ResponseException: ServerError:
java.lang.RuntimeException: java.lang.IllegalStateException:
java.lang.IllegalArgumentException: The provided key is not an element compute
key: gremlin.pageRankVertexProgram.edgeCount
at
Gremlin.Net.Driver.Messages.ResponseStatusExtensions.ThrowIfStatusIndicatesError(ResponseStatus
status) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/Messages/ResponseStatus.cs:line
48
at Gremlin.Net.Driver.Connection.TryParseResponseMessage(ResponseMessage`1
receivedMsg) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/Connection.cs:line
154
at Gremlin.Net.Driver.Connection.Parse(Byte[] received) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/Connection.cs:line
135
--- End of stack trace from previous location where exception was thrown ---
at Gremlin.Net.Driver.ProxyConnection.SubmitAsync[T](RequestMessage
requestMessage) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/ProxyConnection.cs:line
49
at Gremlin.Net.Driver.GremlinClient.SubmitAsync[T](RequestMessage
requestMessage) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/GremlinClient.cs:line
101
at Gremlin.Net.Driver.Remote.DriverRemoteConnection.SubmitBytecodeAsync(Guid
requestid, Bytecode bytecode) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/Remote/DriverRemoteConnection.cs:line
107
at
Gremlin.Net.Driver.Remote.DriverRemoteConnection.SubmitAsync[S,E](Bytecode
bytecode) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/Remote/DriverRemoteConnection.cs:line
80
at Gremlin.Net.Process.Remote.RemoteStrategy.ApplyAsync[S,E](ITraversal`2
traversal) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Remote/RemoteStrategy.cs:line
56
at Gremlin.Net.Process.Utils.WaitUnwrap(Task task) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Utils.cs:line
51
at Gremlin.Net.Process.Remote.RemoteStrategy.Apply[S,E](ITraversal`2
traversal) in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Remote/RemoteStrategy.cs:line
50
at Gremlin.Net.Process.Traversal.DefaultTraversal`2.ApplyStrategies() in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Traversal/DefaultTraversal.cs:line
178
at Gremlin.Net.Process.Traversal.DefaultTraversal`2.GetTraverserEnumerator()
in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Traversal/DefaultTraversal.cs:line
173
at
Gremlin.Net.Process.Traversal.DefaultTraversal`2.get_TraverserEnumerator() in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Traversal/DefaultTraversal.cs:line
66
at Gremlin.Net.Process.Traversal.DefaultTraversal`2.MoveNextInternal() in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Traversal/DefaultTraversal.cs:line
89
at Gremlin.Net.Process.Traversal.DefaultTraversal`2.MoveNext() in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/src/Gremlin.Net/Process/Traversal/DefaultTraversal.cs:line
80
at Gremlin.Net.IntegrationTest.Gherkin.CommonSteps.IterateToList() in
/home/travis/build/apache/tinkerpop/gremlin-dotnet/test/Gremlin.Net.IntegrationTest/Gherkin/CommonSteps.cs:line
143
{code}
Not sure if it's related but intermittent failures in Travis have usually be
caused by the tests executing in a low resource environment. Tests that have
timers, rely on multiple threads, etc. tend to show their problems in Travis.
HadoopMarc had the nice idea to often reliably recreate these errors in Docker
by setting {{cpus=0.9}} - again, unsure if this is the issue, but it would be
nice if we could get to the bottom of this for travis sake but also because it
might be a subtle bug that folks are running into.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
