cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9941) SSTableVerify has wrong return codes on windows
Date Fri, 31 Jul 2015 20:36:04 GMT


Joshua McKenzie commented on CASSANDRA-9941:

Testing on this brought up a different issue: the ccm call to run_sstableverify is actually
checking the contents of the data\ folder on the *root* cassandra installation directory rather
than the ccm nodes. The test was failing out for me on the assertion checking for the failure
text as I was sourcing from a local 2.2 checkout that I'd happened to perform stress on yesterday
which still had data files lying around and it had the KS/CF that this test was looking for.

It's a separate ccm-bug that I'm discussing w/[~philipthompson] offline that shouldn't hold
up inspection of this ticket. I'm out for the next week so if anyone wants to grab this in
the interim, feel free.

> SSTableVerify has wrong return codes on windows
> -----------------------------------------------
>                 Key: CASSANDRA-9941
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Philip Thompson
>            Assignee: Joshua McKenzie
>             Fix For: 2.2.x
> The dtest {{}} is failing on
windows. When running sstableverify.bat on a nonexistent keyspace, the correct error message
is printed, but an error code of 0 for success is returned, which does not match the correct
behavior on linux, which returns 1.

This message was sent by Atlassian JIRA

View raw message