juliangruber / browser-run

Run code inside a browser from the command line
447 stars 62 forks source link

Tests fail on OS X with Node 5: spawn phantomjs ENOENT #102

Closed zeke closed 8 years ago

zeke commented 8 years ago
~/forks/browser-run master
❯ t

> browser-run@3.2.0 test /Users/zeke/forks/browser-run
> make test

test/close.js ......................................... 2/2 967ms
test/empty.js ......................................... 1/1 300ms
test/error.js ......................................... 1/1 469ms
test/phantom.js ....................................... 0/3 30s
  phantomjs
  not ok Error: spawn phantomjs ENOENT
    at:
      line: 890
      column: 11
      file: util.js
      function: exports._errnoException
    stack: |
      exports._errnoException (util.js:890:11)
      _combinedTickCallback (internal/process/next_tick.js:74:11)
      process._tickCallback (internal/process/next_tick.js:98:9)
    code: ENOENT
    errno: ENOENT
    syscall: spawn phantomjs
    path: phantomjs
    spawnargs:
      - '/var/folders/nj/9554mvgj07xdh61jbyhkbtq80000gn/T/phantomjs-stream:4f43af18'
    test: phantomjs
    message: 'Error: spawn phantomjs ENOENT'

  phantomjs
  not ok missing test
  not ok timeout!
    signal: SIGTERM
    handles:
      - type: Server
        events:
          - request
          - connection
          - clientError
        connectionKey: '6::::0'

test/spawn.js ......................................... 1/1 1s
test/stream.js ........................................ 1/1 966ms
total ................................................. 6/9

  6 passing (34s)
  3 failing

make: *** [test] Error 1
npm ERR! Test failed.  See above for more details.

~/forks/browser-run master 36s
❯ node -v
v5.10.1
juliangruber commented 8 years ago

fixed via https://github.com/juliangruber/browser-run/commit/f9b92fdabf5a25bab1c81820ff68f7e1d351a35b