[SERVER-27671] Clean up task storageEngine definitions in evergreen.yml Created: 12/Jan/17  Updated: 07/Mar/18  Resolved: 07/Mar/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.5.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Duplicate Votes: 0
Labels: tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32036 Remove _WT tasks in evergreen.yml Closed
duplicates SERVER-31976 Refactor mmapv1 tests into dedicated ... Closed
Participants:

 Description   

Currently, tasks and variants in everygreen.yml both define the storageEngine argument to resmoke.py. The tasks define either mmapv1 or wiredTiger and a variant that uses a different storage engine would override that.

The override is implicitly enabled by having the resmoke arguments defined for a variant ("test_flags") be passed in later than the resmoke arguments for the task ("resmoke_args").

The side-effect of this ordering is subtle and could cause breakages when we we make changes to how resmoke is invoked.

A better way would be to make the storage engine a variable. E.g.

- <<: *task_template
  name: jsCore
  commands:
  - func: "do setup"
  - func: "run tests"
    vars:
      resmoke_args: --suites=core --storageEngine=mmapv1
      run_multiple_jobs: true

becomes:

- <<: *task_template
  name: jsCore_mmapv1
  commands:
  - func: "do setup"
  - func: "run tests"
    vars:
      resmoke_args: --suites=core
      run_multiple_jobs: true
      task_storage_engine: 'mmapv1'

Variants can similarly define a variant_storage_engine which can then explicitly override the storage engine of the task when constructing resmoke arguments in run_tests (or define task definitions without storage engines)



 Comments   
Comment by Max Hirschhorn [ 07/Mar/18 ]

I believe SERVER-31976 and SERVER-32036 effectively achieved everything this ticket wanted to do.

Generated at Thu Feb 08 04:15:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.