[ 
https://issues.apache.org/jira/browse/CASSANDRA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340790#comment-17340790
 ] 

Andres de la Peña commented on CASSANDRA-16625:
-----------------------------------------------

[~e.dimitrova] Thanks for the review, I've tried to address your suggestions 
and added some additional documentation.

{quote}
Just one thing on my mind, when I hear REPEATED_UTEST_TARGET --> I don't think 
of the in-jvm tests but only about Unit tests so wondering about the naming, 
but I guess when we have the docs and the examples it should be clear.
{quote}
Yeah, I wasn't very sure about what names use for the jobs. Maybe we can use 
{{repeated-java-test}}/{{repeated-python-test}}, or 
{{repeated-junit-test}}/{{repeated-pytest-test}} instead? I used 
{{repeated-utest}}/{{repeated-dtest}} for brevity, which is convenient in tiny 
boxes printed by the CircleCI UI, but I agree that it can be confusing. Perhaps 
we can also use {{junit-multiplexer}}/{{pytest-multiplexer}}, or 
{{java-multiplexer}}/{{python-multiplexer}}, although I'm not sure how the 
usage of "multiplexer" is known outside DS. wdyt?

> 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: 0.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]

Reply via email to