[SERVER-36181] explain_sample.js in core suite must be banned from running in parallel suites for non-WT storage engines Created: 18/Jul/18 Updated: 29/Oct/23 Resolved: 18/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | 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 2018-07-30 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The test expects WT's storage-optimized sample implementation. It is tagged with requires_wiredtiger. However, this is not sufficient, since the parallel suite (basic.js and basicPlus.js) do not consult these tags when selecting jsCore test files. As a result, the parallel suite is failing for the ephemeralForTest build variant. |
| Comments |
| Comment by Githook User [ 18/Jul/18 ] |
|
Author: {'username': 'dstorch', 'name': 'David Storch', 'email': 'david.storch@10gen.com'}Message: |