[
https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341002#comment-17341002
]
Andres de la Peña edited comment on CASSANDRA-16625 at 5/7/21, 6:44 PM:
------------------------------------------------------------------------
{quote}
One thing on my mind, I think when this is committed we need to announce it on
the mailing list to be sure people see it and they start using it as It is a
big win.
I think it would be good also to encourage them to start using it both in case
of failure and when they are adding new tests - pre-commit to be sure they
didn't introduce new flaky test. WDYT?
{quote}
Agree, we should announce this on the dev list. It would be great if repeated
runs were assimilated into the process.
was (Author: adelapena):
{quote}
One thing on my mind, I think when this is committed we need to announce it on
the mailing list to be sure people see it and they start using it as It is a
big win.
I think it would be good also to encourage them to start using it both in case
of failure and when they are adding new tests - pre-commit to be sure they
didn't introduce new flaky test. WDYT?
{quote}
Agree, we should announce this on the dev list. It would be great it if
repeated runs were assimilated into the process.
> 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: 1h 50m
> 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]
