[ https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338894#comment-17338894 ]
Andres de la Peña commented on CASSANDRA-16625: ----------------------------------------------- [~bereng] Indeed JUnit looping needs more work, we should probably go for the bash loop approach for the moment. If at some point we have a working repeated JUnit runner we can easily change the CircleCI config to use it. > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org