Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
failing videomail-client test output
~/b/c/videomail-client ❯❯❯ npm run test ⏎ develop ✭ ✱
> videomail-client@1.20.20 test /home/michael-heuberger/binarykitchen/code/videomail-client
> browserify test/**/*.test.js --debug | tape-run
TAP version 13
# VideomailClient:
# can be instantiated and emits built event
ok 1 should not throw
ok 2 Built event received
# replay without videomail parameter emits error
ok 3 Error event received
# hiding does not throw error and emits event
ok 4 Hide event received
ok 5 should not throw
# unload does not throw an error and emits event
ok 6 should not throw
# Resource:
# can be instantiated
ok 7 should not throw
# AudioRecorder:
# can be instantiated
ok 8 should not throw
# Browser:
# without arguments
npm ERR! Linux 4.8.0-30-generic
npm ERR! argv "/home/michael-heuberger/.nvm/versions/node/v7.2.1/bin/node" "/home/michael-heuberger/.nvm/versions/node/v7.2.1/bin/npm" "run" "test"
npm ERR! node v7.2.1
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! videomail-client@1.20.20 test: `browserify test/**/*.test.js --debug | tape-run`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the videomail-client@1.20.20 test script 'browserify test/**/*.test.js --debug | tape-run'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the videomail-client package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! browserify test/**/*.test.js --debug | tape-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs videomail-client
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls videomail-client
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/michael-heuberger/binarykitchen/code/videomail-client/npm-debug.log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment