[
https://issues.apache.org/jira/browse/CASSANDRA-14421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670687#comment-16670687
]
Ariel Weisberg commented on CASSANDRA-14421:
--------------------------------------------
The very laziest thing to do is to require the environment variables to find
the C* version.
I tried to use fixtures to get the args from the CLI, but the fixtures run
*after* test collection occurs. It's possible to use parameterization to do
this, but the control flow is kind of finicky as I think you have the
opportunity to generate additional parameters after it's already looking at
each individual test case.
> Reenable upgrade tests
> ----------------------
>
> Key: CASSANDRA-14421
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14421
> Project: Cassandra
> Issue Type: Task
> Components: Testing
> Reporter: Sam Tunnicliffe
> Assignee: Ariel Weisberg
> Priority: Major
> Fix For: 4.0
>
>
> Since dtests were switched to pytest & python3 in CASSANDRA-13134, the
> upgrade tests have been non-functional and are deselected by default (though
> even if you ran with the {{--execute-upgrade-tests}} they wouldn't work).
> They're further broken by CASSANDRA-14420, as {{upgrade_manifest}} relies on
> {{CASSANDRA_VERSION_FROM_BUILD}}. We need to get them, or something
> equivalent, up and running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
