[SERVER-35395] Remove Sharding-related 3.6 to 4.0 upgrade/downgrade tests Created: 04/Jun/18  Updated: 29/Oct/23  Resolved: 06/Jun/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-35116 Enumerate and remove Sharding-related... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Participants:

 Description   

These tests are no longer needed, because they test upgrade/downgrade logic specific to 3.6 and 4.0.

  • database_version_upgrade_downgrade.js
  • shard_collection_cache_upgrade_downgrade.js


 Comments   
Comment by Githook User [ 06/Jun/18 ]

Author:

{'username': 'BlakeIsBlake', 'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com'}

Message: SERVER-35395 Remove Sharding-related 3.6 to 4.0 upgrade/downgrade tests
Branch: master
https://github.com/mongodb/mongo/commit/7bed2f2317a8db399530806458dea24b41a1adf8

Comment by Blake Oler [ 05/Jun/18 ]

Removed shard_collection_cache_upgrade_downgrade.js as part of SERVER-34285 because Evergreen was complaining.

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