🚀 Feature: Fail tests/suites that does not exit gracefully when --no-exit flag is used

[TheLudd]

I recently tried the --no-exit flag and found it a terrific way to determine if any of my modules keep active listeners. However, if it is the case that I have open listeners then mocha never exits. Would it be possible to add a timeout just as in asynchronous tests for this. Meaning that if I use the --no-exits flag and the event loop is not clear after my suite is complete, then make the test fail.

I'd be happy to supply this as a PR if the idea is accepted.

[boneskull]

Sounds reasonable to me

[danielstjules]

How would you imagine supplying the timeout for --no-exit?

[TheLudd]

I havent thought about that detail. Would it be possible to use the standard 2000ms and have it changed by globally overriding with --timeout?

[stale]

I am a bot that watches issues for inactivity.
This issue hasn't had any recent activity, and I'm labeling it stale. In 14 days, if there are no further comments or activity, I will close this issue.
Thanks for contributing to Mocha!

[ScottFreeCode]

This issue only seems more relevant now that we've walked people through debugging their --no-exit hangs now that Mocha --no-exits by default.