[SERVER-54674] Use separate replica set test fixtures for each test run in awaitable_hello_fcv_change.js Created: 19/Feb/21 Updated: 29/Oct/23 Resolved: 25/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Ali Mir |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2021-02-22, Repl 2021-03-08 | ||||
| Participants: | |||||
| Linked BF Score: | 14 | ||||
| Description |
|
In awaitable_hello_fcv_change.js, we test the upgrade/downgrade path twice, to test latest <> last-lts and latest <> last-continuous (called here). We perform both test runs on the same replica set. To ensure isolation, we should use separate replica set tests for each run. |
| Comments |
| Comment by Githook User [ 25/Feb/21 ] |
|
Author: {'name': 'Ali Mir', 'email': 'ali.mir@mongodb.com', 'username': 'ali-mir'}Message: |