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

bigeasy / addendum / 42 / 3
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 22 May 2018 02:09AM UTC
Files 1
Run time 0s
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 May 2018 01:26AM UTC coverage: 81.034%. Remained the same
42.3

push

travis-ci

bigeasy
Create a ping timeout helper.

When we do not receive a ping after a certain amount of time we are
supposed to terminate ourselves and not at all gracefully.

This helper class will check a timer and reset it occasionally.

Is is separate for purposes of testing and coverage. Also because when
we replay we're going to want to maybe turn off pinging. Otherwise, we
could just ping on occasion during replay to prevent the ping timeout.

Actually, I'm wondering about this as I create it. Why are we adding a
timer to the application when we're going to admonish the user to always
use the API to preserve a log for replay?

I suppose because network timeouts are part of the network layer. If
this was a persistent socket it would have a timeout built into it. We
would have to occasionally send a keep-alive message.

0 of 4 branches covered (0.0%)

47 of 58 relevant lines covered (81.03%)

1.76 hits per line

Source Files on job 42.3
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 35
  • Travis Job 42.3
  • 52bf4c9d on github
  • Prev Job for on master (#41.1)
  • Next Job for on master (#43.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