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

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

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

16 Oct 2018 12:11PM UTC coverage: 59.569% (+0.001%) from 59.568%
COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS=""

push

travis-ci

nmathewson
mainloop: Set client role if ControlPort is set

It turns out that if _only_ the ControlPort is set and nothing else, tor would
simply not bootstrap and thus not start properly. Commit 67a41b63063370c2
removed that requirement for tor to be considered a "client".

Unfortunately, this made the mainloop enable basically nothing if only the
ControlPort is set in the torrc.

This commit now makes it that we also consider the ControlPort when deciding
if we are a Client or not. It does not revert 67a41b63063370c2 meaning
options_any_client_port_set() stays the same, not looking at the control port.

Fixes #27849.

Signed-off-by: David Goulet <dgoulet@torproject.org>

41500 of 69667 relevant lines covered (59.57%)

27409.59 hits per line

Source Files on job 2465.5 (COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="")
  • Tree
  • List 0
  • Changed 52
  • Source Changed 1
  • Coverage Changed 52
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 1577
  • Travis Job 2465.5
  • b5731cdf on github
  • Prev Job for COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="" on maint-0.3.4 (#2456.5)
  • Next Job for COVERAGE_OPTIONS="--enable-coverage" HARDENING_OPTIONS="" on maint-0.3.4 (#2477.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