Process-related utility code should have unit test coverage over 95%

x/procmon.c.gcov 45 0 0.00
x/util_process.c.gcov 5 33 86.84

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified points::3 priority::medium resolution::implemented severity::normal sponsor::S-can status::closed testing tor-tests-coverage tor-tests-unit type::enhancement labels

Trac:
Milestone: N/A to Tor: 0.2.8.x-final

Trac:
Keywords: testing SponsorS deleted, testing, 028-triage, SponsorS added

Bulk-replace SponsorS keyword with SponsorS sponsor field in Tor component.

Trac:
Keywords: SponsorS deleted, N/A added
Sponsor: N/A to SponsorS

Trac:
Points: N/A to medium

update:

procmon.c.gcov 13 28 68.29
util_process.c.gcov 2 38 95.00

We're getting there...

Trac:
Severity: N/A to Normal

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

Trac:
Milestone: Tor: 0.2.8.x-final to Tor: 0.2.9.x-final

Trac:
Sponsor: SponsorS to SponsorS-can

Trac:
Keywords: N/A deleted, tor-tests-coverage, tor-tests-unit added

Trac:
Points: medium to 3

Trac:
Milestone: Tor: 0.2.9.x-final to N/A
Parent: #16791 (moved) to #17289 (moved)

Trac:
Reviewer: N/A to N/A
Status: new to assigned
Owner: N/A to andrea

Trac:
Milestone: N/A to Tor: unspecified
Owner: andrea to N/A

Trac:
Status: assigned to new

Unparenting.

Trac:
Parent: #17289 (moved) to N/A

Trac:
Keywords: 028-triage deleted, N/A added

These modules are over 75% now, and are no longer logging seriously behind the rest of the world. Closing.

Trac:
Status: new to closed
Resolution: N/A to implemented

*lagging

closed

changed time estimate to 24h

moved to tpo/core/tor#16795 (closed)