Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-17912

Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.0.29, 3.11.15, 4.0.8, 4.1-rc1
    • CI
    • None
    • Correctness - Test Failure
    • Normal
    • Normal
    • User Report
    • All
    • None
    • Hide

      This is the last 3.0 patch and run

      • 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

       

      Show
      This is the last 3.0 patch  and run 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  

    Description

      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 - 3.0 run

      Jenkins - while typing this I actually noticed one test 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. 

      Attachments

        Issue Links

          Discovered while testing

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-17885 Add solution for CASSANDRA-17581 to older branches for tests

          • Normal -
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-17760 upgrade_tests/upgrade_udtfix_test.py failing in Circle CI for Cassandra 3.0 and 3.11

          • Normal -
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-17760 upgrade_tests/upgrade_udtfix_test.py failing in Circle CI for Cassandra 3.0 and 3.11

          • Normal -
          • Resolved

          Task - A task that needs to be done. CASSANDRA-17930 Ensure CircleCI and ASF Jenkins CI are aligned

          • Normal -
          • In Progress

          Activity

            People

              e.dimitrova Ekaterina Dimitrova
              e.dimitrova Ekaterina Dimitrova
              Ekaterina Dimitrova
              Michael Semb Wever
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: