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

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

{quote} As Ekaterina Dimitrova says under j8 section we have j11 tests to test 
that cross-jvm combination. What I was referring to is that under the j11 
section the j11 unit tests should not require approval. I makes no sense to me 
that j11/cqlsh and j11/jvm_dtests don't require approval and always triggered 
automatically but the j11/junit does. Would you guys agree?
{quote}
I agree, it makes sense to me to automatically start j11 unit tests for j11 
builds, since we already do that with cqlsh and jvm_dtests. There is a comment 
in that part of the config saying that running j11 unit tests is currently not 
working 
([here|https://github.com/adelapena/cassandra/commit/61ba75d405d64d9c1c60f11be554de1b88ecd622#diff-bc7cfdde47dcf913bec381c90c03b51e430f1e4b34ff2ac1c419d87436c85137L265]).
 Maybe they were originally set as optional just because they didn't work at 
the time of writing that part of the file? 

> 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