[
https://issues.apache.org/jira/browse/CALCITE-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570876#comment-16570876
]
Julian Hyde commented on CALCITE-2442:
--------------------------------------
I was using JDK 10 early access, which gave version as "10". Upgrading to
"10.0.2" seemed to fix the problem for JDK 10.
However, the same fix did not work for OpenJDK 10. I am now on OpenJDK 10.0.2
and the problem seems to still occur. I get
{noformat}
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0 s <<<
FAILURE! - in org.apache.calcite.test.CassandraAdapterTest
[ERROR] org.apache.calcite.test.CassandraAdapterTest Time elapsed: 0 s <<<
FAILURE!
java.lang.AssertionError: Cassandra daemon did not start within
timeout{noformat}
I suspect that there is a cassandra instance still running from another test.
How can I detect that? Netstat or ps, perhaps?
> Cassandra unit test leaves stale folders in cassandra/ module on Windows
> ------------------------------------------------------------------------
>
> Key: CALCITE-2442
> URL: https://issues.apache.org/jira/browse/CALCITE-2442
> Project: Calcite
> Issue Type: Bug
> Components: cassandra
> Reporter: Andrei Sereda
> Priority: Major
>
> [~Sergey Nuyanzin] reported that
> [CassandraUnit|https://github.com/jsevellec/cassandra-unit] leaves
> {{.toDelete}} folder in maven module folder ({{cassandra/}}) rather than
> {{target/}} where all build and temporary files should be located.
> {quote}
> There is one more strange thing (at least on Windows): while building a
> file with name ".toDelete" is generated under calcite\cassandra and it's
> not removed by the end of tests
> Is there a way to make cassandra generates these files in target directory
> e.g.?
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
