[SERVER-36233] Prohibit running the "profile" command from secondary read override test suites. Created: 20/Jul/18 Updated: 29/Oct/23 Resolved: 09/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.2.20 |
| Fix Version/s: | 4.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | 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, v3.4, v3.2
|
||||||||
| Sprint: | TIG 2018-07-30, TIG 2018-08-13 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 5 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Running the profile command can cause system.profile to be created. Since system.profile is an unreplicated collection, there is no point in testing it in secondary read override test suites. It can also cause other tests to pick up the unreplicated collection and fail. We should prevent the profile command from being run in the set_read_preference_secondary.js override file. |
| Comments |
| Comment by Githook User [ 09/Aug/18 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}Message: |
| Comment by Max Hirschhorn [ 20/Jul/18 ] |
|
Maybe the jstests/core/dbhash.js test isn't the problem. Perhaps we should be banning tests which run the "profile" command as part of the set_read_preference_secondary.js function override? I think because I saw failures when working on |