Opened 5 years ago

Last modified 2 years ago

#11145 new defect

coverage utility should merge multiple output files

Reported by: nickm Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: tor-client, coverage, tools, testing, SponsorS-deferred
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

When multiple gcov invocations generate output for the same file (typically a header), we should combine their results rather than letting the last invocation win.

Child Tickets

Change History (17)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.7.x-final

These may be worth looking at for 0.2.7.

comment:2 Changed 4 years ago by nickm

Status: newassigned

comment:3 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking some tickets as triaged-in for 0.2.7 based on early triage

comment:4 Changed 4 years ago by isabela

Keywords: SponsorS added
Points: small
Priority: minortrivial
Version: Tor: 0.2.7

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:6 Changed 4 years ago by nickm

Keywords: SponsorS removed
Sponsor: SponsorS

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

comment:7 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:8 Changed 3 years ago by isabela

Sponsor: SponsorSSponsorS-can

comment:9 Changed 3 years ago by nickm

Keywords: SponsorS-deferred added
Sponsor: SponsorS-can

Remove the SponsorS status from these items, which we already decided to defer from 0.2.9. add the SponsorS-deferred tag instead in case we ever want to remember which ones these were.

comment:10 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:11 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:12 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:13 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:14 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:15 Changed 2 years ago by nickm

Keywords: 027-triaged-1-in removed

comment:16 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:17 Changed 2 years ago by nickm

Keywords: tools testing added
Severity: Normal
Note: See TracTickets for help on using tickets.