You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran express' master tests against Mocha's current master branch (via dont-break), and the tests did not complete (the Node.js process hangs).
This is likely because of a forthcoming change in v4 which will cause Mocha to not force exit its own process once it's finished running tests (by default). See this issue for more background.
If I had to hazard a guess, likely one or more of Express' tests are leaving socket(s) open instead of closing them explicitly.
If Express wishes to upgrade, its options are:
Audit the tests and ensure they are not leaving any sockets, servers, etc., open/listening when they complete, or
Revert to pre-v4 behavior by supplying the --exit option to Mocha
The text was updated successfully, but these errors were encountered:
Thanks for the notification! From my understanding mocha 4 won't work under Node.js 0.10 anyway, so we won't be upgrading master to that version anyway, but Express 5 would end up upgrading, though, so would need to be addressed at that time.
I ran express'
master
tests against Mocha's currentmaster
branch (via dont-break), and the tests did not complete (the Node.js process hangs).This is likely because of a forthcoming change in v4 which will cause Mocha to not force exit its own process once it's finished running tests (by default). See this issue for more background.
If I had to hazard a guess, likely one or more of Express' tests are leaving socket(s) open instead of closing them explicitly.
If Express wishes to upgrade, its options are:
--exit
option to MochaThe text was updated successfully, but these errors were encountered: