[
https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343166#comment-17343166
]
Andres de la Peña commented on CASSANDRA-16625:
-----------------------------------------------
Thanks for the reviews, committed to 3.0 as
[a01cbfdce5e6b8959b792b3f693f87c2fc8f6b92|https://github.com/apache/cassandra/commit/a01cbfdce5e6b8959b792b3f693f87c2fc8f6b92]
and merged up to
[3.11|https://github.com/apache/cassandra/commit/1e42c105ce31613a8c5e94e4c2d4c817e12a4dce],
[4.0|https://github.com/apache/cassandra/commit/98b449f38aa5a5ae64d030c1f437847a3c938cee]
and
[trunk|https://github.com/apache/cassandra/commit/f637198484c74b71429b1bc884d3fe9a86a4a926].
> 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: 2.5h
> 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]
