[
https://issues.apache.org/jira/browse/CASSANDRA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349310#comment-17349310
]
Ekaterina Dimitrova commented on CASSANDRA-16687:
-------------------------------------------------
{quote}As it's mentioned in the description, supporting Python upgrade dtests
is easy, we only need to add the {{--execute-upgrade-tests}} as it's done
[here|https://github.com/apache/cassandra/pull/1016/commits/d5966428453e225510bfc0caa28eb1723dd56ee5].
If I'm right this flag is harmless when the repeated test to be run isn't an
upgrade test.
{quote}
Indeed, it is harmless but I think it will be confusing to have the multiplexer
for python dtests and python upgrade tests at one job.
Why? Because I am +1 on your option number 5 and because everywhere we have
separately run any upgrade tests in a loop or not. I think it will be
consistent and less confusing for the user to separate them. WDYT?
> Support upgrade tests in CircleCI multiplexer
> ---------------------------------------------
>
> Key: CASSANDRA-16687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16687
> 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
>
> The CircleCI jobs for running a test repeatedly added by CASSANDRA-16625
> don't support upgrade tests. In the case of Python upgrade dtests we only
> need the {{--execute-upgrade-tests}} when calling {{pytest}}. For Java
> upgrade tests we need to build the dtest jars before running the repeated
> tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
