cassandra-commits mailing list archives

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

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

Currently broken by CASSANDRA-7066 (thus depending on CASSANDRA-10109). Error message from
CI yesterday was:
File "D:\Python27\lib\unittest\", line 329, in run
  File "D:\jenkins\workspace\cassandra-3.0_dtest_win32\cassandra-dtest\",
line 15, in udt_test
  File "build\\egg\ccmlib\", line 249, in start
    p = node.start(update_pid=False, jvm_args=jvm_args, profile_options=profile_options)
  File "build\\egg\ccmlib\", line 447, in start
  File "build\\egg\ccmlib\", line 343, in check_socket_available
    raise UnavailableSocketError("Inet address %s:%s is not available: %s" % (addr, port,
'Inet address is not available: [Errno 10013] An attempt was made to access
a socket in a way forbidden by its access permissions\n-------------------- >> begin
captured logging << --------------------\ndtest: DEBUG: cluster ccm directory: d:\\temp\\dtest-dpsz3i\n---------------------
>> end captured logging << ---------------------'

Failure history: [regression in build #17|].
Doesn't look like there was any real change to explain that though.

Env: Not sure if repro locally since CASSANDRA-7066 error is in the way. 

This message was sent by Atlassian JIRA

View raw message