[SERVER-33269] add --excludeWithAnyTags=requires_mmapv1 to every non-MMAPv1 builder Created: 12/Feb/18  Updated: 29/Oct/23  Resolved: 28/Feb/18

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-37816 [3.6] Add --excludeWithAnyTags=requir... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-02-26, Repl 2018-03-12
Participants:
Linked BF Score: 0

 Description   

With recover to stable timestamp, some tests will only work on mmapv1. We can either delete them and lose test coverage, or tell WT builders to ignore these tests.



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

Author:

{'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}

Message: SERVER-33269: Fix windows async evergreen variant to only declare one `test_flags`
Branch: master
https://github.com/mongodb/mongo/commit/c9f2d8059206de3ded12beca2b08a9be3d1f9b13

Comment by Githook User [ 28/Feb/18 ]

Author:

{'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}

Message: SERVER-33269 add --excludeWithAnyTags=requires_mmapv1 to every non-MMAPv1 builder
Branch: master
https://github.com/mongodb/mongo/commit/1e89f1ba964d1989dfef74e189926d47a5c930c9

Comment by Max Hirschhorn [ 12/Feb/18 ]

With recover to stable timestamp, some tests will only work on mmapv1. We can either delete them and lose test coverage, or tell WT builders to ignore these tests.

Another option would be to have conditional logic in the test itself to return early if jsTest.options().storageEngine !== "mmapv1".

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