[SERVER-29906] Resmoke should support derived suites Created: 28/Jun/17  Updated: 06/Dec/22

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

Type: New Feature Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 1
Labels: stm, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Many of our suites are really just some other suite with a single small change. As an example, I'd like to introduce sharding_jscore_passthrough_opquery which is the same as sharding_jscore_passthrough, except it sets executor.config.shell_options.rpcProtocols to opQueryOnly. Unfortunately this requires duplicating the whole file which almost guarantees that they will fall out of sync in the future.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Mathias Stearn [ 18/Jul/17 ]

Given that I already committed https://github.com/mongodb/mongo/commit/013f374c9d055cf434102fad2b6bfd83bb7616a9, this isn't a burning problem for me. It just seems like something that would improve our testing situation.

Comment by Max Hirschhorn [ 18/Jul/17 ]

Max Hirschhorn can you clarify why this is in debugging with submitter? Are you waiting on something from Mathias?

ian.whalen, I was curious if Mathias was comfortable having this sit on our backlog and instead (1) have a separate ticket for adding a --shellRpcProtocols option to resmoke.py for testing OP_MSG and (2) move SERVER-18395 from Backlog to 3.5 Desired.

Comment by Ian Whalen (Inactive) [ 17/Jul/17 ]

max.hirschhorn can you clarify why this is in debugging with submitter? Are you waiting on something from Mathias?

Comment by Max Hirschhorn [ 29/Jun/17 ]

redbeard0531, I think that if we were to tag the tests to exclude from the sharding_jscore_passthrough.yml suite (SERVER-18395), then would be less of an issue. There's been ideas of having separate test suites for the MMAPv1 and WiredTiger versions of the same test suite (i.e. the Evergreen tasks) so that exclusions can be done on a storage engine-specific level. The other way I could see this going is to introduce a --shellRpcProtocols option to resmoke.py that sets shell_options.rpcProtocols like you described.

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