Any way to end a feature test successfully when nodejs hangs?

[totty90]

I have a quite big app that hangs because of sockets. It doesn't end the feature and cucumber hangs. Is possible to force end the feature but with success?

[jbpros]

I can't think of any straightforward way to do that reliably without losing some part of the output from Cucumber. Isn't it possible to close the sockets properly (which would be the right way of doing things anyway)?

[kaworu]

see also #262

[kaworu]

I have the same issue as you do. In my case, the problem is that another npm module (connection-mongostore) keep an open connection. The module does not offer any way to close it. While Cucumber hanging is fine when tests are run from the cli it's a real issue with CI (like Jenkins).

Leaving aside the Right Way™ debate, I am not sure that it is reasonable to think that all third parties module will cleanup or offer a way to do it. When one of them does not it's a world of pain to figure out which and why.

@totty90 as a workaround I am stuck using cucumber =0.4.0, which was the latest version that did not hang.

[totty90]

@kaworu why the newer version hangs?

[kaworu]

@totty90 as I've written in #262 the fix is 1da47fb which reference #120.

[jbpros]

Should be fixed by 23ff860. Please reopen is necessary.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.