[SERVER-48091] Clean up resmoke arguments Created: 11/May/20  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Vlad Rachev (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-47611 Re-work to_local_args function using ... Closed
Assigned Teams:
Server Tooling & Methods
Participants:
Story Points: 3

 Description   
  • Create --inEvergreen option instead of relying on --taskId to avoid ambiguity around how to get resmoke to behave in a certain way when running in Evergreen. Note that --inEvergreen should not be part of the evergreen argument group because we want to be able to set it even for local runs when reproducing an Evergreen failure.
  • Remove options that save values to the same dest variables. Eg. -shuffle and -shuffleMode.
  • Send an email to kernel@10gen when the above is done.
  • Look through existing options list and move appropriate options to advanced_options to improve the --help clutter. See Raiden's comment in this CR (internal) for more info


 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 Vlad Rachev (Inactive) [ 11/May/20 ]

We should discuss whether we want the "local usage ..." command printed by resmoke to run a test identically locally and on evergreen (with the same timeouts, hooks and other configurations). We could then have the --inEvergreen option be used to specify that the local behavior should match evergreen behavior completely. The evergreen_options group in parser.py would then be used to store args needed for scheduling, reporting and running tasks in evergreen but have no bearing on how the test is actually run.

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