[
https://issues.apache.org/jira/browse/TINKERPOP-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318834#comment-17318834
]
Marc de Lignie commented on TINKERPOP-2504:
-------------------------------------------
I pushed [some
changes|[https://github.com/vtslab/incubator-tinkerpop/tree/TINKERPOP-2504]|https://github.com/vtslab/incubator-tinkerpop/tree/TINKERPOP-2504]
that make the GremlinServerAuthKrb5IntegrateTest,
GremlinServerAuditLogIntegrateTest and
GremlinServerAuditLogDeprecatedIntegrateTest succeed in a cocker container with
--cpus=".9" . This still does not complete the gremlin-server build, so their
may be other problems (see below). Also, my changes only work around some other
issue with gremlin-driver that has a blocking thread on connection failure or
does not have the right timeout configs (but I guess we do not have to solve
this here).
For completeness I list the failsafe-report from the docker container while it
hangs on some other issue:
root@50b4e89febc5:/usr/src/tinkerpop/gremlin-server/target# ls
failsafe-reports/*.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinResultSetIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogDeprecatedIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerAuthIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerAuthKrb5IntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerAuthzIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerSessionIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinServerSslIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.GremlinSessionTxIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.channel.HttpChannelizerIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.channel.WebSocketChannelizerIntegrateTest.txt
failsafe-reports/org.apache.tinkerpop.gremlin.server.channel.WsAndHttpChannelizerIntegrateTest.txt
root@50b4e89febc5:/usr/src/tinkerpop/gremlin-server/target#
Probably it fails on GremlinDriverIntegrateTest which also uses the
addContactPoint() method.
> Intermittently failing server/driver integration tests
> ------------------------------------------------------
>
> Key: TINKERPOP-2504
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2504
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver, server
> Affects Versions: 3.4.9
> Reporter: Stephen Mallette
> Priority: Minor
>
> I've noticed this test failing intermittently on Travis and more consistently
> on the {{master}} branch with Docker. It fails with a
> {{ConcurrentModificationException}} (haven't been able to easily get the
> entire stack trace thanks to the docker issue and i've not caught it
> happening in the last few days on Travis). Adding this line of code seems to
> have made the test pass more consistently:
> https://github.com/apache/tinkerpop/commit/4b099b3c84a350aae953cdf517aa11c7017eb2ae
> which would indicate something perhaps fishy with how hosts are being marked
> dead and iterated. Would be nice to get rid of that little hack.
> Another common failure that is fairly consistent is with
> {{GremlinServerAuditLogIntegrateTest.shouldAuditLogWithKrb5Authenticator}}
> {code}
> [ERROR]
> shouldAuditLogWithKrb5Authenticator(org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogIntegrateTest)
> Time elapsed: 3.16 s <<< ERROR!
> java.util.concurrent.ExecutionException:
> org.apache.tinkerpop.gremlin.driver.exception.ResponseException:
> Authenticator is not ready to handle requests
> at
> org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogIntegrateTest.shouldAuditLogWithKrb5Authenticator(GremlinServerAuditLogIntegrateTest.java:222)
> Caused by: org.apache.tinkerpop.gremlin.driver.exception.ResponseException:
> Authenticator is not ready to handle requests
> {code}
> cc/ [~divijvaidya] [~HadoopMarc]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
