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

ooni / netx / 126 / 3
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: issue/302
DEFAULT BRANCH: master
Ran 22 Oct 2019 09:12AM UTC
Files 23
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 Oct 2019 09:06AM UTC coverage: 100.0%. Remained the same
GO111MODULE=on

push

travis-ci-com

bassosimone
httpx: use context for propagating transaction info

The final barrier for using context for propagating transaction info
is the usage of DialTLS inside the http transport.

By switching to using DialContext instead, and by delegating to the
net/http transport the TLS handshake, we can propagate the context
everywhere, so we can always put measurements in context.

While working on that, I realised that the split between a TLS
handshake start and a TLS handshake done event was reasonable since
it allowed us to put I/O events between these two events in the
right context (i.e. TLS handshake I/O) as well.

In the same vein, I should probably split the Resolve event into
two separate events, to put resolve operations in context.

991 of 991 relevant lines covered (100.0%)

27.58 hits per line

Source Files on job 126.3 (GO111MODULE=on)
  • Tree
  • List 0
  • Changed 2
  • Source Changed 0
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 211
  • Travis Job 126.3
  • dbd15e74 on github
  • Prev Job for GO111MODULE=on on feature/refactor-10 (#126.3)
  • Next Job for GO111MODULE=on on feature/refactor-10 (#128.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