cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-10109) Windows dtest 3.0: failures
Date Mon, 17 Aug 2015 20:59:45 GMT
Joshua McKenzie created CASSANDRA-10109:

             Summary: Windows dtest 3.0: failures
                 Key: CASSANDRA-10109
             Project: Cassandra
          Issue Type: Sub-task
            Reporter: Joshua McKenzie
             Fix For: 3.0.x

Errors locally are different than CI from yesterday. Yesterday on CI we have timeouts and
general node hangs. Today on all 3 tests when run locally I see:
Traceback (most recent call last):
  File "c:\src\cassandra-dtest\", line 532, in tearDown
    raise AssertionError('Unexpected error in %s node log: %s' % (, errors))
AssertionError: Unexpected error in node1 node log: ['ERROR [main] 2015-08-17 16:53:43,120 - This platform does not support atomic directory streams (SecureDirectoryStream);
race conditions when loading sstable files could occurr']

This traces back to the commit for CASSANDRA-7066 today by [~Stefania] and [~benedict].  Stefania
- care to take this ticket and also look further into whether or not we're going to have issues
with 7066 on Windows? That error message certainly *sounds* like it's not a good thing.

This message was sent by Atlassian JIRA

View raw message