[SERVER-19868] Clean up how we set the storage engine for replset config servers in resmoke.py for the sharding_passthrough suites Created: 11/Aug/15 Updated: 06/Dec/16 Resolved: 06/Dec/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Max Hirschhorn |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | TIG 2016-12-12 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
As part of |
| Comments |
| Comment by Max Hirschhorn [ 06/Dec/16 ] |
|
I'm closing this ticket as "Won't fix" because the current way we hardcode this logic in resmoke.py doesn't seem problematic given that we still only support running a CSRS with the WiredTiger storage engine. |