Handle socket hangup

[missinglink]

On slow connections the socket can hangup. The following happened in the car, on 3g.

events.js:71
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: socket hang up
    at createHangUpError (http.js:1373:15)
    at CleartextStream.socketCloseListener (http.js:1424:23)
    at CleartextStream.EventEmitter.emit (events.js:93:17)
    at SecurePair.destroy (tls.js:956:22)
    at process.startup.processNextTick.process._tickCallback (node.js:245:9)

[sebinsua]

This is actually happening to me on my local OSX machine for some reason.

[missinglink]

Thanks for the feedback @Bedtimes, does it happen intermittently or all the time?

[sebinsua]

It seems to depend on how many requests I am testing. It is bad enough that I can reproduce every single time unless I specify that I am testing only a very specific section of the app - which is an acceptable workaround in the short-term.

[sebinsua]

As a tangent, even if the socket does hang-up for some reason or other, it would be more robust to be able to see the list of tests which have passed and failed up to the point of network failure.

[missinglink]

Thanks for that, it sounds like this issue affects OSX more than nix. I'll mark it as priority as it sounds like it can be annoying for your workflow.

Re: the network issues, it is most likely because of the parallelism of requests and assertions, since ciao is designed for speed of test execution, it's likely maxing out the OS at some point.

I'll likely mark those tests as an error instead of a fail and continue the rest of the tests.

[sebinsua]

Thanks for that, it sounds like this issue affects OSX more than nix. [...] It is most likely because of the parallelism of requests and assertions, since ciao is designed for speed of test execution, it's likely maxing out the OS at some point.

Yes. Another thing that might help you with support for OSX is that I was originally receiving a "Error: spawn EMFILE" from child_process.js. I was able to fix this by running "ulimit -n 10000" on the shell before executing ciao.

[sebinsua]

This is happening all of the time for me now. I've no idea why...

Edit: Can you give me any pointers on what file I should be debugging?

[missinglink]

That's very odd, are you sure the services are available via cURL?

[fabriziomoscon]

@missinglink this might be related to #35

[sebinsua]

^ Fab is correct, this was related to #35.

[missinglink]

@Bedtimes @fabriziomoscon I just pushed a fix for #35 which should resolve this issue in ciao 0.2.3.

Please upgrade: [sudo] npm install ciao -g and confirm that the fix is valid.

[missinglink]

I'm leaving this ticket open as the Exception is still not being caught.