Details
Description
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
[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
Attachments
Issue Links
- depends upon
-
TINKERPOP-2550 Deadlock on Client initialization
- Closed
- is duplicated by
-
TINKERPOP-2553 Intermittently failing Kerberos tests
- Closed