[SERVER-32938] update ns_length.js to use different collection name for each test case Created: 26/Jan/18 Updated: 27/Oct/23 Resolved: 13/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In passthrough suites, it's hard to tell at what stage in the test the base collection in ns_length.js is being replicated to secondaries. Additionally, having the same name might result in conflicting rename operations being applied to the same namespace (due to index namespace restrictions for example). |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 13/Mar/20 ] |
|
This test no longer exists. |