You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Andrei Sereda (JIRA)" <ji...@apache.org> on 2018/08/03 19:06:00 UTC

[jira] [Commented] (CALCITE-2442) Cassandra unit test leaves stale folders in cassandra/ module on Windows

    [ https://issues.apache.org/jira/browse/CALCITE-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16568626#comment-16568626 ] 

Andrei Sereda commented on CALCITE-2442:
----------------------------------------

[~julianhyde] and [~michaelmior] can you please detail errors you're seeing while running cassandra tests in your environment (based on this branch) ? I know you have mentioned something on the dev list, but test code have changed since. 

Ideally full stack trace with environment details (OS, JDK, #CPUs etc.) 

> 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)