[SERVER-35523] FSMWorkloadTestCase erroneously sets TestData.sameDB=true and TestData.sameCollection=true Created: 09/Jun/18 Updated: 29/Oct/23 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Robert Guo (Inactive) |
| 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 | ||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||
| Sprint: | TIG 2018-07-02, TIG 2018-07-16 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The logic in the FSMWorkloadTestCase class is faulty because it sets TestData.sameDB=true when same_db=false and TestData.sameCollection=true when same_collection=false. However, these options currently have no effect because resmoke_runner.js doesn't define clusterOptions.sameDB and clusterOptions.sameCollection based on their associated TestData equivalents.
|
| Comments |
| Comment by Githook User [ 05/Jul/18 ] |
|
Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}Message: (cherry picked from commit 5c73ea14a6fb2b5a9c071ad5d987b2dc900d12df) |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'guoyr', 'name': 'Robert Guo', 'email': 'robert.guo@10gen.com'}Message: |
| Comment by Max Hirschhorn [ 09/Jun/18 ] |
|
Follow-up comment: |