[SERVER-32858] Add Evergreen tasks back to Linux (No Journal) builder Created: 23/Jan/18  Updated: 30/Oct/23  Resolved: 09/Mar/18

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

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Ian Whalen (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

As part of the changes from SERVER-31976, several Evergreen tasks were moved to the MMAPv1 builder due to the contents of the Linux (No Journal) being a mixture of running certain tasks with the WiredTiger storage engine and other tasks with the MMAPv1 storage engine.

Due to the changes from SERVER-30347, we've since realized the importance of having a Linux (No Journal) MMAPv1 builder (SERVER-32798). I think we should add what would have been the WiredTiger-equivalent of the Evergreen tasks to both the master and 3.6 branches. However, given the changes from SERVER-30347, the list for the master branch is a subset of the list for the 3.6 branch.

  • jsCore_compatibility
  • noPassthrough
  • noPassthroughWithMongod
  • bulk_gle_passthrough
  • parallel
  • parallel_compatibility
  • concurrency
  • concurrency_replication (3.6 only)
  • concurrency_sharded (3.6 only)
  • concurrency_simultaneous
  • replica_sets (3.6 only)
  • replica_sets_auth (3.6 only)
  • replica_sets_jscore_passthrough (3.6 only)
  • master_slave_jscore_passthrough (both, until SERVER-32143)
  • sharding (3.6 only, per removal of sharding_auth in SERVER-32769)
  • slow1
  • serial_run
  • sharding_jscore_passthrough
  • tool


 Comments   
Comment by Githook User [ 09/Mar/18 ]

Author:

{'email': 'ian.whalen@gmail.com', 'name': 'Ian Whalen', 'username': 'IanWhalen'}

Message: SERVER-32858 Add Evergreen tasks back to Linux (No Journal) builder
Branch: master
https://github.com/mongodb/mongo/commit/becfcd51e5eaec45dc1c8da1f61dc9fd06f5fb9a

Comment by Ian Whalen (Inactive) [ 23/Jan/18 ]

Putting in Needs Triage just to make sure the Storage team reviews this and we schedule as needed.

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