Opened 6 months ago

Last modified 2 months ago

#29490 new defect

Chutney fails (sometimes?) when tor is built with --enable-coverage

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: CI, tor-ci, 041-deferred-20190530, ex-sponsor-19, ex-sponsor19
Cc: teor Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Right now we can't enable chutney on Travis when Tor is built with --enable-coverage. This appears to be relating to timing issues with consensus generation. I can reproduce this behavior on my desktop.

Child Tickets

Change History (6)

comment:1 Changed 3 months ago by nickm

Keywords: tor-ci added; removed

comment:2 Changed 3 months ago by nickm

Keywords: 041-deferred-20190530 added

Marking these tickets as deferred from 041.

comment:3 Changed 3 months ago by nickm

Milestone: Tor: 0.4.1.x-finalTor: unspecified

comment:4 Changed 3 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:5 Changed 3 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

comment:6 Changed 2 months ago by teor

Parent ID: #29280
Note: See TracTickets for help on using tickets.