• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

ethereum / web3.js / 3006 / 4
84%
1.x: 80%

Build:
Build:
LAST BUILD BRANCH: wyatt/rename-eth2-packages
DEFAULT BRANCH: 1.x
Ran 22 Sep 2018 10:33PM UTC
Files 38
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

22 Sep 2018 10:28PM UTC coverage: 82.839% (-0.2%) from 83.011%
CXX=g++-4.8 TEST_SUITE=test

Pull #1966

travis-ci

web-flow
Try to reconnect on timeout too

In the case any websocket call takes too long to return and a timeout
was set for the provider to timeout, the provider should try to restart
the connection.

This could happen, for instance, if the client loses connection with the
server, the server closes the connection and later, the connectivity is
up again but since the client did not receive the closing frame *and*
the client does not attempt to send any package to the server, no error
is observed.

`websocket` implementation for Node.js has an option to send keep-alive
frames and detect such scenarios, but the standard browser W3C WebSocket
does not, so it is "vulnerable" to this kind of failure which will
mostly affect web3 subscriptions.
Pull Request #1966: Full support for websocket reconnection/resubscription

1128 of 1532 branches covered (73.63%)

2124 of 2564 relevant lines covered (82.84%)

541.77 hits per line

Source Files on job 3006.4 (CXX=g++-4.8 TEST_SUITE=test)
  • Tree
  • List 0
  • Changed 4
  • Source Changed 3
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 2638
  • Travis Job 3006.4
  • 9e4fba26 on github
  • Prev Job for CXX=g++-4.8 TEST_SUITE=test on reconnect-resubscribe (#2939.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc