[SERVER-72929] Make resmoke fixtures compatible with last-lts/continuous Created: 17/Jan/23  Updated: 29/Oct/23  Resolved: 10/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Tausif Rahman (Inactive) Assignee: Trevor Guidry
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-60947 concurrency_sharded_replication_multi... Closed
Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 0

 Description   
  • Stop checking out resmoke fixtures from last-lts/last-continuous branches for multiversion testing on master & upgrade the existing resmoke fixtures on master to be compatible with last-lts & last-continuous at all times
  • Appendix: Stop Checking out Resmoke Fixtures


 Comments   
Comment by Githook User [ 10/May/23 ]

Author:

{'name': 'Trevor Guidry', 'email': 'trevor.guidry@mongodb.com', 'username': ''}

Message: SERVER-72929 do not checkout old resmoke fixtures
Branch: master
https://github.com/mongodb/mongo/commit/5e2159ea02bdfc56de4d5998f784f70e83777e0a

Comment by Tausif Rahman (Inactive) [ 17/Apr/23 ]

You will probably want to run some form of the future git tag variant to confirm that your changes do not break multiversion infrastructure. https://github.com/10gen/mongo/blob/def26be32afa18c0b318f53ca669435612161d9f/etc/evergreen.yml#L1843

There could be preexisting test failures for tests that are not passing on the new version, but you should not have resmoke fixture failures. For instance, here is a recent failing task in the "future git tag" variant: https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_80_64_bit_future_git_tag_multiversion_display_multiversion_future_git_tag_5facb9a7c4e98a7636e061544ad9d359302d9847_23_04_11_03_58_24

^ If you based your changes off of that base commit, you should have the same failures.

You will need to figure out whether you need to set this via evergreen patch parameter here to truly test your changes. I'm not 100% sure. https://github.com/10gen/mongo/blob/8ebd13ecaecdd2d437afea7d2fe1d7a4b8d5e52c/etc/evergreen_yml_components/definitions.yml#L36 

Comment by Tausif Rahman (Inactive) [ 07/Feb/23 ]

BF-24325 & BF-23000 were originally supposed to be resolved by SERVER-60947 but the BFs have since gone away and SERVER-60947 is no longer needed. These BFs/Tickets are all due to the fundamental problem of "git checkout" of last-lts/continuous fixtures. SERVER-72929 will solve that problem.

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