Requirements

• Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• All new code requires tests to ensure against regressions.

Description of the Change

<!--

We must be able to understand the design of your change from this description. Keep in mind that the maintainers and/or community members reviewing this PR may not be familiar with the subsystem. Please be verbose.

-->

Alternate Designs

<!-- Explain what other alternates were considered and why the proposed version was selected -->

Why should this be in core?

<!-- Explain why this functionality should be in mocha as opposed to its own package -->

Benefits

<!-- What benefits will be realized by the code change? -->

Possible Drawbacks

<!-- What are the possible side-effects or negative impacts of the code change? -->

Applicable issues

<!--

• Enter any applicable Issues here.

• Mocha follows semantic versioning: http://semver.org

• Is this a breaking change (major release)?

• Is it an enhancement (minor release)?

• Is it a bug fix, or does it not impact production code (patch release)? -->

Fixes https://github.com/mochajs/mocha/issues/4390

From what I'm seeing it's a bit more subtle. It seems to me that it does finish loading, but some of the pipes are broken. Specifically it handles key presses, executes the commands, and does pipe the output. It doesn't seem to pipe the prompt to the console, or hook the magic keys (like arrow up etc.) (I can confirm the regression happens with build 20150 and is still happening in build 20161)

Maybe @bitcrazed or @craigaloewen can help triage this?