cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-12277) Extend testing infrastructure to handle expected intermittent flaky tests - see ReplicationAwareTokenAllocatorTest.testNewCluster
Date Fri, 22 Jul 2016 16:23:20 GMT
Joshua McKenzie created CASSANDRA-12277:
-------------------------------------------

             Summary: Extend testing infrastructure to handle expected intermittent flaky
tests - see ReplicationAwareTokenAllocatorTest.testNewCluster
                 Key: CASSANDRA-12277
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12277
             Project: Cassandra
          Issue Type: Bug
            Reporter: Joshua McKenzie
            Assignee: Branimir Lambov
            Priority: Minor


>From an offline discussion:

bq. The ReplicationAwareTokenAllocatorTest.testNewCluster failure is a flake -- randomness
will sometimes (on the order of 1/100) cause it to fail. Extending the ranges to avoid these
flakes goes too far and makes the test meaningless.

bq. How about instead of @flaky/@Ignore which currently indicates a test that intermittently
fails but we do not expect it to, we instead use @tries, or @runs, or some annotation that
indicates "run this thing N times, if M pass we're good". This would allow us to keep the
current "we don't care about these test results (in context of green test board) because intermittent
failures are not expected and the test quality needs shoring up" from "we expect this test
to fail sometimes in this particular way."



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

Mime
View raw message