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

torproject / tor / 2477 / 5
60%
master: 66%

Build:
Build:
LAST BUILD BRANCH: maint-0.4.3
DEFAULT BRANCH: master
Ran 17 Oct 2018 05:36PM UTC
Files 437
Run time 13min
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

17 Oct 2018 04:25PM UTC coverage: 59.569%. Remained the same
COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS=""

push

travis-ci

dgoulet-tor
conn: Stop writing when our write bandwidth limist is exhausted

Commit 488e2b00b introduced an issue, most
likely introduced by a bad copy paste, that made us stop reading on the
connection if our write bandwidth limit was reached.

The problem is that because "read_blocked_on_bw" was never set, the connection
was never reenabled for reading.

This is most likely the cause of #27813 where bytes were accumulating in the
kernel TCP bufers because tor was not doing reads. Only relays with
RelayBandwidthRate would suffer from this but affecting all relays connecting
to them. And using that tor option is recommended and best practice so many
many relays have it enabled.

Fixes #28089.

41500 of 69667 relevant lines covered (59.57%)

27565.45 hits per line

Source Files on job 2477.5 (COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="")
  • Tree
  • List 0
  • Changed 51
  • Source Changed 1
  • Coverage Changed 50
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1586
  • Travis Job 2477.5
  • 2000d04c on github
  • Prev Job for COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="" on maint-0.3.4 (#2465.5)
  • Next Job for COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="" on maint-0.3.4 (#2493.5)
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