[SERVER-48016] Blacklist version2.js from multiversion testing Created: 07/May/20 Updated: 29/Oct/23 Resolved: 29/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-06-01 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Description |
|
The version2.js test doesn't make sense to test multiversion scenarios – it creates a one-shard cluster and tests directly against that shard. Given the fact that we also plan on deprecating and removing setShardVersion, this test may not be around much longer anyway. |
| Comments |
| Comment by Githook User [ 29/May/20 ] |
|
Author: {'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}Message: |