[SERVER-15970] command line option --durOptions not working Created: 05/Nov/14  Updated: 11/Jul/16  Resolved: 05/Nov/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 2.8.0-rc0

Type: Bug Priority: Blocker - P1
Reporter: Ian Whalen (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

e.g. https://mci.10gen.com/task/mongodb_mongo_master_osx_108_debug_b0d74105634a3a2040743061c53b0e5b4eff919d_14_11_05_17_04_07_durability_osx_108_debug



 Comments   
Comment by Daniel Pasette (Inactive) [ 05/Nov/14 ]

For the record, I misunderstood and thought that the failures were for WiredTiger :/

Comment by Githook User [ 05/Nov/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-15970 --durOptions was not working
Branch: master
https://github.com/mongodb/mongo/commit/ecd562289fa27fcd50fb63c3d1cfb0925c5ae2f9

Comment by Eric Milkie [ 05/Nov/14 ]

All the durability failures appear to be the same thing: a command line option conflict. Probably easy to fix, so I recommend we just fix it and don't touch suite configs.

Comment by Daniel Pasette (Inactive) [ 05/Nov/14 ]

My take on this is that we should do a bulk move of the failing tests to the mmapv1 directory and re-assess right afterwards so we can clear the runway for the RC. Same goes for disk.

Alternatively, we just switch these suites off for WT now, and examine them individually if some of them actually apply to both WT and MMAPv1.

Now that I think about it, we should go with the second plan.

Generated at Thu Feb 08 03:39:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.