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
Running npm test or directly running node test/header-test.js hangs. This occurs when running on Linux, and (as reported by @BigBlueHat in #61 (comment)) on bash on Windows in mingw, but interestingly does not hang in cmd.
Here's the output I get on Linux, even after left running for 10 minutes:
$ npm test
> [email protected] test /home/jade/src/thornjad/union
> vows test/*-test.js --spec -i
♢ union/after
When using union a union server with after middleware
✓ should preserve the request until the last call
♢ union/body-parser
When using union with connect body parsing via urlencoded() or json() a request to /
✓ should respond with a body-decoded object
♢ union/double-write
When using union an http server which attempts to write to the response twice a GET request to /foo
✓ it should respond with { 'hello': 'world' }
✓ it should not write to the response twice
When the tests are over
✓ the server should close
♢ union/ecstatic
When using union with ecstatic a request to /404.txt (which does not exist)
✓ should respond with 404 status code
When using union with ecstatic a request to /some-file.txt
✓ should respond with hello world
♢ union/header
The text was updated successfully, but these errors were encountered:
Running
npm test
or directly runningnode test/header-test.js
hangs. This occurs when running on Linux, and (as reported by @BigBlueHat in #61 (comment)) on bash on Windows in mingw, but interestingly does not hang in cmd.Here's the output I get on Linux, even after left running for 10 minutes:
The text was updated successfully, but these errors were encountered: