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

Ekaterina Dimitrova edited comment on CASSANDRA-16625 at 4/28/21, 2:47 PM:
---------------------------------------------------------------------------

{quote}Good idea, done 
[here|https://github.com/adelapena/cassandra/commit/61ba75d405d64d9c1c60f11be554de1b88ecd622]
 for the j11 workflow. By the way, I'm not sure why we have j11 jobs in the j8 
workflow.
{quote}
I don't think it is a bug to require J11 unit tests to be run. This should be a 
minimum for J11 support.

And we have J11 jobs on the J8 build as it exercises the case build on Java 8, 
run in Java 11. Check table 1 
[here|https://cassandra.apache.org/doc/latest/new/java11.html?highlight=support%20matrix].


was (Author: e.dimitrova):
{quote}Good idea, done 
[here|https://github.com/adelapena/cassandra/commit/61ba75d405d64d9c1c60f11be554de1b88ecd622]
 for the j11 workflow. By the way, I'm not sure why we have j11 jobs in the j8 
workflow.
{quote}
I don't think it is a bug to require J11 unit tests to be run. This should be a 
minimum for J11 support.

And we have J11 jobs on the J8 run as it exercises the case build on Java 8, 
run in Java 11. Check table 1 
[here|https://cassandra.apache.org/doc/latest/new/java11.html?highlight=support%20matrix].

> 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