For god know what reason (couldn't reproduce locally, tried every trick in the book), boltkit shutting down Neo4j after the ITs would timeout consistently in TeamCity. Since the service is (at least currently) started and stopped for the whole test session, not per test, there's little risk in just killing it instead of gracefully shutting it down.
For god know what reason (couldn't reproduce locally, tried every trick in the book), boltkit shutting down Neo4j after the ITs would timeout consistently in TeamCity. Since the service is (at least currently) started and stopped for the whole test session, not per test, there's little risk in just killing it instead of gracefully shutting it down.