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

Ekaterina Dimitrova commented on CASSANDRA-16625:
-------------------------------------------------

* The addition of  {{passes}}/{{fails}} prefix to the artifacts' paths plus the 
run number is a huge win IMHO. Thank you! It will save us time definitely.
 * Good catch to make the run of J11 unit tests a requirement.
 * Great catch fixing the _generate.sh_ script to add the license header when 
we update the files!

 +1, just added a few small formatting suggestions. 

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.

As part of this ticket or a separate one, I think we should update at least 
this page, otherwise we risk people not to know about this multiplexer which 
could help us in many, many cases to save time - 
[https://cassandra.apache.org/doc/latest/development/testing.html?highlight=testing]

 

> 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]

Reply via email to