[
https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339582#comment-17339582
]
Andres de la Peña commented on CASSANDRA-16625:
-----------------------------------------------
[~bereng] that run repeats the entire {{DirectoriesTest}} suite 10K times.
Since the suite has 15 tests, the number of run tests is 150K. The env var
[{{REPEATED_UTEST_METHODS}}|https://github.com/apache/cassandra/blob/0ff4e086dfada6b63f0c7b44551e6e53b902d5b2/.circleci/config-2_1.yml#L53]
can be used to run only {{DirectoriesTest#testSecondaryIndexDirectories}}, but
I left it blank in case something in the other tests was producing the failure.
> Add a CircleCI job to run some tests repeatedly
> -----------------------------------------------
>
> Key: CASSANDRA-16625
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16625
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I think it could be useful to have an optional CircleCI job to run some
> specific tests n times. That way, tickets could attach CircleCI runs showing
> that the changes don't make a certain ticket flaky or, conversely, that they
> fix a flaky test. Doing this systematically should mitigate the risk of
> introducing new flaky tests, and I guess it would be more convenient and easy
> to share than running the tests locally or on a private CI system.
> It would also be nice to have something similar in Jenkins, but I'm focusing
> this ticket on CircleCI because it's available also for non-committers, so
> assignees can run their tests before setting the tickets as ready for review.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
