[SERVER-64320] resmoke command in evergreen log doesn't capture multiversion-related extra options Created: 08/Mar/22  Updated: 06/Dec/22  Resolved: 05/May/22

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

Type: Bug Priority: Major - P3
Reporter: Maddie Zechar Assignee: [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-66059 Fix multiversion task generation issues Closed
Assigned Teams:
Decision Automation Group
Operating System: ALL
Sprint: DAG 2022-05-02, DAG 2022-05-16
Participants:

 Description   

The local usage reported for multiversion evergreen task (link here) doesn't currently capture the extra options you need for multi-version related tasks. In my case, I needed to add `--suite=generated_resmoke_config/sharding_last_continuous_1.yml` to my resmoke command to replicate the evergreen results locally.



 Comments   
Comment by Max Hirschhorn [ 24/Mar/22 ]

I'm not sure why the Evergreen-generated suite definitions should ever need to be downloaded. My expectation is https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1804_debug_ubsan_sharding_multiversion_last_continuous_1_ubuntu1804_debug_ubsan_9b2fe8666c8a633ed141b86676116094d2a468cb_22_02_10_11_09_51 would report --suite=sharding_last_continuous instead of --suites=sharding. I feel like SERVER-64320 is a bug with how the concept of matrix_suites interfaces with --originSuite used to generated the local resmoke.py usage arguments.

Comment by Iryna Zhuravlova [ 24/Mar/22 ]

The command is expected to work with reproducing individual failed tests; for running the entire suite, the Evergreen-generated suite definitions don't need to be downloaded.

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