[
https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17912:
--------------------------------------------
Test and Documentation Plan:
This is the last 3.0
[patch|https://github.com/apache/cassandra/compare/cassandra-3.0...ekaterinadimitrova2:cassandra:17912-3.0?expand=1]
and
[run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1971/workflows/8eb3b149-a84b-4f76-a061-e15df972492e/jobs/15600]
* removed extra_env_args: 'RUN_STATIC_UPGRADE_MATRIX=true' (making us run all
possible tests, this one should be removed in another ticket CASSANDRA-16348
directly from the DTEST repo) and tests_filter_pattern: '^upgrade_tests' (which
was filtering to run only tests from the upgrade_tests dir but we have some
also in the main dir)
* changed to run the tests with DEBUG and not INFO, same we do in Jenkins and
other branches. Easier for debugging
* propagated the changes to MIDRES and HIGHRES too and recreated the patch
files even if they were still applicable. Otherwise we get confusing warnings
when we raise resources without any real issue.
Compared Jenkins and CircleCI and revised what tests get collected - only
updating from and to 3.0
was:
This is the last 3.0
[patch|https://github.com/apache/cassandra/compare/cassandra-3.0...ekaterinadimitrova2:cassandra:17912-3.0?expand=1]
and
[run|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1971/workflows/8eb3b149-a84b-4f76-a061-e15df972492e/jobs/15600]
* removed extra_env_args: 'RUN_STATIC_UPGRADE_MATRIX=true' (making us run all
possible tests, this one should be removed in another ticket CASSANDRA-16348
directly from the DTEST repo) and tests_filter_pattern: '^upgrade_tests' (which
was filtering to run only tests from the upgrade_tests dir but we have some
also in the main dir)
* changed to run the tests with DEBUG and not INFO, same we do in Jenkins and
other branches. Easier for debugging
* propagated the changes to MIDRES and HIGHRES too and recreated the patch
files even if they were still applicable. Otherwise we get confusing warnings.
Compared Jenkins and CircleCI and revised what tests get collected - only
updating from and to 3.0
> Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
> --------------------------------------------------------------------
>
> Key: CASSANDRA-17912
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17912
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
> It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11
> Python upgrade tests. Those are properly skipped in Jenkins.
> Example runs:
> [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293]
> - 3.0 run
> [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/]
> - while typing this I actually noticed [one
> test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/]
> only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we
> test 3.0...
> This is good to be fixed for two reasons - reduce the noise so we do not miss
> legit failures and we should not spend resources to try to run those tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
