[
https://issues.apache.org/jira/browse/CASSANDRA-18567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729748#comment-17729748
]
Ekaterina Dimitrova commented on CASSANDRA-18567:
-------------------------------------------------
Currently, we don't :) Jenkins does not have enough energy for all of them (for
reference CASSANDRA-18499)
My plan Is to add them and they can be optional pre-commit in CircleCI but
always run in Jenkins post-commit. Same as the current Python upgrade tests
We do not have in Jenkins tests that run on a particular cadence. Everything
runs post-commit there, as far as I know.
> Add jobs for resource-intensive Python upgrade tests
> ----------------------------------------------------
>
> Key: CASSANDRA-18567
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18567
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>
> As it was noticed in CASSANDRA-18499, Python upgrade tests should include
> resource-intensive ones. Some are run in CircleCI but skipped in Jenkins (see
> CASSANDRA-18499 for reference).
> We should add --skip-resource-intensive-tests to the current Python upgrade
> tests jobs and create new jobs dedicated to the resource-intensive upgrade
> tests — the way we do it for the regular Python Dtests(for reference - large
> DTests).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
