[SERVER-37623] Cannot set MongoRunner.mongodPath or MongoRunner.mongosPath and run multiversion tests or test commands Created: 13/Oct/18  Updated: 06/Dec/22  Resolved: 05/Nov/21

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

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: tig-mongorunner, tig-multiversion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Tooling & Methods
Operating System: ALL
Participants:

 Description   

resmoke.py supports setting --mongod and --mongos command line options to have MongoRunner use those binaries when spawning mongod and mongos binaries, respectively. This behavior interferes with multiversion testing (i.e. binVersion != "latest") because the path to the mongod-* executables are resolved relative to the MongoRunner.mongodPath path even though they are meant to be findable on the PATH.

The work on this ticket would involve not using MongoRunner.mongodPath or MongoRunner.mongosPath when binVersion != "latest", and to instead use "mongod" and "mongos" as the binaryName.

Additionally, the appendSetParameterArgs() function should modified to treat "path/to/mongod" and "mongod" as the latest version. The baseProgramName needs to actually get the basename of the programName variable.



 Comments   
Comment by Brooke Miller [ 05/Nov/21 ]

This hasn't come up recently. We have related work to make shell fixtures more integrated with resmoke, which won't solve this problem directly, but we hope to unlock others ability to accomplish this.

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