cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10638) logged_batch_compatibility tests fail on Windows
Date Thu, 05 Nov 2015 17:10:28 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko updated CASSANDRA-10638:
------------------------------------------
    Fix Version/s:     (was: 3.0.0)
                   3.1

> logged_batch_compatibility tests fail on Windows
> ------------------------------------------------
>
>                 Key: CASSANDRA-10638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10638
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jim Witschey
>            Assignee: Paulo Motta
>             Fix For: 3.1
>
>
> A number of the batch tests fail on Windows with a couple different errors. On one build,
they all fail with a pair of errors, e.g.:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/101/testReport/batch_test/TestBatch/logged_batch_compatibility_2_test_2/
> and
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/101/testReport/batch_test/TestBatch/logged_batch_compatibility_2_test/
> I can't tell if this is a C* failure or an environment issue, where the node fails to
start after being upgraded.
> On other runs, the tests flap when the test fails to delete temporary files. Consider
the failures here:
> http://cassci.datastax.com/view/win32/job/cassandra-3.0_dtest_win32/100/testReport/batch_test/
> It could be an environmental issue, but I think I'd expect to see this error in in other
tests, but I haven't yet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message