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

ooni / netx / 269 / 1
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 28 Oct 2019 06:53PM UTC
Files 27
Run time 5s
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

28 Oct 2019 06:51PM UTC coverage: 100.0%. Remained the same
GO111MODULE=on

push

travis-ci-com

web-flow
Make events actionable for OONI's nervous system (#78)

After trial and error, I have determined that, in general, to decide
whether we need follow-up measurements, we need just the result of
four events in the HTTP round trip:

- RESOLVE_DONE
- CONNECT
- HANDSHAKE_DONE
- ROUND_TRIP_DONE

In some cases it may be possible to run operations inline while in
others it's probably best to run concurrently or later.

Regardless of the implementation strategy, this diff makes sure that
by combining this four events only, we have enough information to
conclude whether to trigger more measurements.

This conclusion is based on my analysis using ooni/jafar, it may be
of course that later we'll need to tweak this a bit.

I've been doing refactoring for quite some time to prepare this.

Master issue: https://github.com/ooni/probe-engine/issues/87

1400 of 1400 relevant lines covered (100.0%)

43.5 hits per line

Source Files on job 269.1 (GO111MODULE=on)
  • Tree
  • List 0
  • Changed 5
  • Source Changed 0
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 493
  • Travis Job 269.1
  • 518daf98 on github
  • Prev Job for GO111MODULE=on on master (#269.1)
  • Next Job for GO111MODULE=on on master (#272.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