web3jse2eTest.output

  Web3 e2e tests
    Web3 integration tests for: http://ganache:8545
      ✓ should be able to make a web3 instance
      ✓ should be able to get a list of accounts (157ms)
    Web3 integration tests for: http://geth:8545
      ✓ should be able to make a web3 instance
      ✓ should be able to get a list of accounts
    Web3 integration tests for: ws://geth:8546
      ✓ should be able to make a web3 instance
connection not open on send()
      1) should be able to get a list of accounts
    Web3 integration tests for: http://parity:8545
      ✓ should be able to make a web3 instance
      ✓ should be able to get a list of accounts
    Web3 integration tests for: ws://parity:8546
      ✓ should be able to make a web3 instance
      ✓ should be able to get a list of accounts


  9 passing (11s)
  1 failing

  1) Web3 e2e tests
       Web3 integration tests for: ws://geth:8546
         should be able to get a list of accounts:
     Error: connection not open
      at WebsocketProvider.send (packages/web3-providers-ws/src/index.js:276:18)
      at RequestManager.send (packages/web3-core-requestmanager/src/index.js:132:66)
      at sendRequest (packages/web3-core-method/src/index.js:560:42)
      at Eth.send [as getAccounts] (packages/web3-core-method/src/index.js:581:13)
      at Context.it (e2e/generic-tests.js:18:45)



npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] e2e:mocha: `mocha --recursive ./e2e/**/*.spec.js -R spec --exit`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] e2e:mocha script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-04-16T09_18_49_167Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] e2e: `docker-compose down && docker-compose build && docker-compose run --entrypoint 'npm run e2e:mocha' test_runner`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] e2e script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/petro/.npm/_logs/2019-04-16T09_18_49_997Z-debug.log