[SERVER-29457] profile_sampling.js should not be run during initial sync passthrough suite Created: 06/Jun/17 Updated: 30/Oct/23 Resolved: 09/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | David Storch |
| 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: | Query 2017-06-19 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The 'replica_sets_initsync_jscore_passthrough' suite has a secondary node syncing during the other tests, so tests that interact with the profiler cannot be run during this suite. Many such tests are already blacklisted, but this list does not include profile_sampling.js. profile_sampling.js failed in one of my patch builds because it saw an extra profile entry. We should think about how to prevent new tests that interact with the profile from failing similarly. |
| Comments |
| Comment by Githook User [ 09/Jun/17 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |