Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45500

Fix backport exclude logic from multiversion tests for new test files

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.3
    • Affects Version/s: 4.3 Required
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2020-01-13, Repl 2020-01-27

      Currently, there are two bugs related to the exclude test logic used by the etc/backports_required_for_multiversion.yml:

      1. Test files are not being excluded from burn_in_multiversion even if they are blacklisted using etc/backports_required_for_multiversion.yml. This is because burn_in_multiversion will generate the exclude_files section in the generated suite yaml files but still call the resmoke command to run the new tests. The command line options passed through this resmoke command will override any configurations specified in the suite yaml. We should avoid generating resmoke commands for excluded files altogether for burn_in_multiversion.

      2. New test files are not being excluded properly (when excluded using etc/backports_required_for_multiversion.yml) from burn_in_multiversion because of the way the suite yaml files are generated. New files will fall under the suite_misc.yml file which specifies a glob as its selector (as opposed to specific test files in the other generated suites). We need to update the exclude_files section in the generated misc suites to include files excluded using etc/backports_required_for_multiversion.yml.

            Assignee:
            jason.chan@mongodb.com Jason Chan
            Reporter:
            jason.chan@mongodb.com Jason Chan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: