[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: |
|
||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
| Comments |
| Comment by Githook User [ 10/May/23 ] |
|
Author: {'name': 'Trevor Guidry', 'email': 'trevor.guidry@mongodb.com', 'username': ''}Message: |
| 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 |