[SERVER-35163] Unblacklist and Fix tests that expect FCV version to differ between "last-stable" and "latest" Created: 22/May/18 Updated: 29/Oct/23 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.0.0-rc0 |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-07-02, Sharding 2018-07-16 |
| Participants: |
| Description |
|
Since we update the FCV independently from the server version, there is a period of time when "last-stable" and "last" server versions have the same FCV version. We have a number of tests that expect their FCV versions to be different; these tests should be modified to check the FCV version on "last-stable" and downgrade to an older FCV if needed. The FCVs are defined in jstests/libs/feature_compatibility_version.js as of the writing of this ticket. |
| Comments |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'BlakeIsBlake', 'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com'}Message: |