[SERVER-25022] Re-enable --fork tests in logpath.js Created: 12/Jul/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Logging, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin Pulo | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
There are some tests in noPassthroughWithMongod/logpath.js which have been disabled on account of These tests should be re-enabled. They will need to be updated for changes that have happened to the test suite in the interim, eg. MongoRunner opts of { fork: true } will translate to cmdline args of "--fork true", and so { fork: "" } needs to be used instead. Also stopping the process via MongoRunner.stopMongod() doesn't seem to work as expected (though manually connecting and shutting down should work). |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |