You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/07/25 17:51:00 UTC

[jira] [Commented] (CALCITE-2442) Cassandra unit test intermittent failures

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

Stamatis Zampetakis commented on CALCITE-2442:
----------------------------------------------

I get the impression that the current PR already fixed a couple of problems.

[~sereda] Should we merge it as is and treat the remaining problems in another case?

> Cassandra unit test intermittent failures
> -----------------------------------------
>
>                 Key: CALCITE-2442
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2442
>             Project: Calcite
>          Issue Type: Bug
>          Components: cassandra-adapter
>            Reporter: Andrei Sereda
>            Priority: Major
>              Labels: pull-request-available
>
> We have noticed that there are failures due to : 
> # Wrong parsing of new [JDK version scheme|http://openjdk.java.net/jeps/223] (by calcite and cassandra dependencies like jamm). {{10-ea}} vs {{10.0.2}} 
> # Cassandra startup timeout on Linux Jenkins CI server. Contrary to github travis CI (the one which validates PRs), it takes about 20s for embedded cassandra to start (still under investigation).
> # [~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. Not a failure but annoyance. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)