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 front-end tests
{ [Error: Command failed: ] killed: false, code: 1, signal: null }
info: Testacular server started at http://localhost:9876/
info (launcher): Starting browser .travis/chrome-start.sh
debug (launcher): Creating temp dir at /tmp/testacular-60857050
debug (launcher): .travis/chrome-start.sh http://localhost:9876/?id=60857050
debug (watcher): Resolved files:
/home/travis/build/ging/licode/node_modules/testacular/adapter/lib/jasmine.js
/home/travis/build/ging/licode/node_modules/testacular/adapter/jasmine.js
/home/travis/build/ging/licode/extras/basic_example/public/erizo.js
/home/travis/build/ging/licode/test/nuve-test.js
warn (launcher): .travis/chrome-start.sh have not captured in 10000 ms, killing.
debug (launcher): Cleaning temp dir /tmp/testacular-60857050
info (launcher): Trying to start .travis/chrome-start.sh again.
debug (launcher): Creating temp dir at /tmp/testacular-60857050
debug (launcher): .travis/chrome-start.sh http://localhost:9876/?id=60857050
warn (launcher): .travis/chrome-start.sh have not captured in 10000 ms, killing.
debug (launcher): Cleaning temp dir /tmp/testacular-60857050
info (launcher): Trying to start .travis/chrome-start.sh again.
debug (launcher): Creating temp dir at /tmp/testacular-60857050
debug (launcher): .travis/chrome-start.sh http://localhost:9876/?id=60857050
warn (launcher): .travis/chrome-start.sh have not captured in 10000 ms, killing.
debug: .travis/chrome-start.sh failed to capture, aborting the run.
info: Disconnecting all browsers
debug: Waiting for child processes to finish
debug (launcher): Cleaning temp dir /tmp/testacular-60857050
Build and installs are OK, but it fails on launching tests.
The text was updated successfully, but these errors were encountered:
It's difficult to make this kind of complex applications to properly work in Travis due to workload and real time requirements, so we won't use in the future. Anyway, we'll include more accurate tests that can be run with the following command once installed:
When Travis runs a test, it ends with:
Build and installs are OK, but it fails on launching tests.
The text was updated successfully, but these errors were encountered: